Get started

Initial steps to start using our Access APIs.


Prerequisite: Get your Access Worldpay credentials from yourImplementation managerand make yourself familiar with ourAPI principles.

Set your headers

Setting your headers is an important part of an API request. The headers represent the meta-data associated with your API request.

Copied!
Authorization: {your_credentials}
Content-Type: {API specific Content-Type header}
Accept: {API specific Accept header}
HeaderDescription
AuthorizationThe Authorization header is used for authentication and identification of our merchants within Access Worldpay. You must use the Authorization header for any requests you send to our APIs.
Content-TypeThe Content-Type header is required if the request you're sending includes a request body, and if the HTTP method is a POST or a PUT.
AcceptThe Accept header is used to identify which version of our API you are using. You must use the Accept header for any requests you send to our APIs.

Query the root resource

Our APIs guide you by providing you with links to the next available actions.

To discover and start using our APIs you must first query the root resource. This returns the available resources within Access Worldpay.

Request

For testing (try)

GET https://try.access.worldpay.com/

For live

GET https://access.worldpay.com/

Note: No request body is needed for this request.

Response

You receive all our available API resources in the response.

Copied!
{
    "_links": {
        "payments:authorize": {
            "href": "https://try.access.worldpay.com/payments/authorizations"
        },
        "service:payments": {
            "href": "https://try.access.worldpay.com/payments"
        },
        "service:tokens": {
            "href": "https://try.access.worldpay.com/tokens"
        },
        "service:verifications/accounts": {
            "href": "https://try.access.worldpay.com/verifications/accounts"
        },
        "service:verifications/customers/3ds": {
            "href": "https://try.access.worldpay.com/verifications/customers/3ds"
        },
        "service:verifiedTokens": {
            "href": "https://try.access.worldpay.com/verifiedTokens"
        },
        "service:payouts": {
            "href": "https://try.access.worldpay.com/payouts"
        },
        "curies": [{
            "href": "https://try.access.worldpay.com/rels/payments/{rel}",
            "name": "payments",
            "templated": true
        }]
    }
}
{
    "_links": {
        "payments:authorize": {
            "href": "https://access.worldpay.com/payments/authorizations"
        },
        "service:payments": {
            "href": "https://access.worldpay.com/payments"
        },
        "service:tokens": {
            "href": "https://access.worldpay.com/tokens"
        },
        "service:verifications/accounts": {
            "href": "https://access.worldpay.com/verifications/accounts"
        },
        "service:verifications/customers/3ds": {
            "href": "https://access.worldpay.com/verifications/customers/3ds"
        },
        "service:verifiedTokens": {
            "href": "https://access.worldpay.com/verifiedTokens"
        },
        "service:payouts": {
            "href": "https://access.worldpay.com/payouts"
        },
        "curies": [{
            "href": "https://access.worldpay.com/rels/payments/{rel}",
            "name": "payments",
            "templated": true
        }]
    }
}

Query the resources to discover the specific API. The response contains links to your next available actions and the corresponding resources.

Note: When you query the root resource, you may notice that some resources are only available in Try and not in Live. This is because the API is still under development and is available for preview only.

When integrating into Access Worldpay, we strongly recommend that you get the URI resource links from the action links. Do not hard code the URI resource links, they could change and break your integration.

An action link is a parameter where the URI link to the resource is stored.

A URI resource link is the link to the resource you send your requests to.

Example

Copied!
"payments:authorize": {
            "href": "https://try.access.worldpay.com/payments/authorizations"
}

In the example above, the action link is:

payments:authorize

and the URI resource link is:

https://try.access.worldpay.com/payments/authorizations

This resource is to the paymentsauthorizationresource.

DNS Whitelisting

Whitelist the following URLs:

  • https://try.access.worldpay.com/
  • https://access.worldpay.com/

Alternatively you can whitelist the following IPs:

Copied!
151.101.2.47
151.101.66.47
151.101.130.47
151.101.194.47

We recommend that you use DNS whitelisting over explicit IP whitelisting.

Documentation

The following documentation covers your test integration and the latest versions of our APIs. Once you've completed and tested your integration into your selected APIs, see ourgo livedocumentation.