GET acquisition context by id

Retrieve an acquisition context by its id

Request

Resource URL

GET https://api.ft.com/acquisition-contexts/{acquisitionContextId}

For security reasons requests must be made over HTTPS.

Parameters

Path paramMandatoryValue
acquisitionContextId
Yes The unique identifier for the acquisition context which is to be retrieved

Request Headers

HeaderValue
X-Api-Key <API key value>

Request Body

Not supported.

Response

200 - OK

{  
   "AcquisitionContext": 
    {"signupContext": 
        {"accessLicenceId": "aca9e27f-2a58-496c-b94d-bc84dffa6f5c",
             "allowedEmailDomains": [],
         "restrictEmailDomains": false,
                 "blockedEmailDomains": [],
         "restrictBlockedEmailDomains": false,
                 "signupWelcomeText": "This is the signup welcome text for Test-Next licence."
             },
         "barrierContext":
        {"promptUserToJoin": true,
                 "subHeading": "TEST-Next has purchased a group subscription to FT.com.",
                 "bodyText": "Join now, sucka80.  This is the Test-Next barrier body text.",
                 "redirectUrl": "https://join.ft.com/6a89e58d-09bd-4b59-9c21-64172ffe9f7b",    
             "displaySignupUrl": true
             },
         "id": "e95e952d-36fd-4db2-8fe2-c326fd1241d5",
         "name": "TEST-Next",
         "allowedIPRanges": ["87.81.147.169"],
         "restrictIPRanges": false,
         "displayName": "TEST-Next",
         "logoUrl": null,
         "marketable": true,
         "lastUpdated": "2016-11-09T13:53:08.366Z"
     }
}

400 - Bad Request

{    "code": 400,    "message": "Parameter is not a UUID."}

HTTP Status Codes

Http StatusDescription
200 Ok A wrapped acquisition context object is returned
400 Bad request The request was invalid. You may refer to response for details around why the request was invalid
403 Forbidden Invalid API key used
404 Not Found No acquisition context exists for the acquisitionContextId provided

Make sure you are using a valid API key. If you are sure your are using a valid API key and problems persist, contact us for assistance.