Checkout Authentication

General

The Checkout Authentication API, also known as the Authentication API, serves the purpose of registering and logging in customers, including guest customers without passwords, as well as resetting a customer's password. This API enables you to:

• Acquire an access token, which grants you the ability to both retrieve and modify customer data via the Customer Account API
• Initiate the checkout process with the Webcomponent
• View all active sessions for a given customer and invalidate specific tokens or sessions.

To implement custom login and registration forms, as well as the password reset flow on your storefront, you'll need to make calls from your frontend to your backend. Subsequently, your backend will communicate with the Authentication API.

This guide provides you with the necessary information to seamlessly integrate with the Authentication API, elucidating key concepts and relevant endpoints. For specific endpoint details, refer to the Authentication API specification.

Authentication API

Create an API Client in the SCAYLE Panel

Before you can interact with the Authentication API, you have to create an API client in the SCAYLE Panel to obtain your client_id and client_secret.

To create a token:

1. Navigate to Shops > Storefront > API keys.
2. Click + Generate OAuth Credentials.
3. Enter a Name and click Create Token.

Make sure to store those credentials safely in your backend. All the endpoints explained in the following chapters require you to provide the client_id and client_secret as a Basic Auth header on the request.

Example

Authorization: Basic {base64Encode({client_id}:{client_secret})}

Authenticate using the Authentication API

The Authentication API offers various endpoints, each requiring different authentication methods based on the use case:

• Basic Auth: Utilize OAuth Client credentials for secure access.
• Bearer Auth: Employ Access Tokens for authenticated requests.
• No Auth: Some endpoints are publicly accessible without authentication.

Consult theAPISpecification for detailed authentication requirements for each endpoint.

For endpoint access, use the following host: https://{{tenant-space}}.auth.scayle.cloud

Responses

Authentication API HTTP Status Codes and Error Handling

The Authentication API uses HTTP status codes to signify the outcome of API requests:

• 2xx: Successful operations.
• 4xx: Failures due to incorrect or insufficient information provided by the user.
• 5xx: Errors originating from Authentication API's servers.

In the event of an error, Authentication API issues an error response with error details. Typically, this includes a single error, but some endpoints may return multiple errors.

For a comprehensive understanding, refer to the following tables detailing status codes, error responses, and error entities.

HTTP status codes