CreateAccessor - Amazon Managed Blockchain



The token based access feature is in preview release for Ethereum on Amazon Managed Blockchain and is subject to change. We recommend that you use this feature only with test scenarios, and not in production environments.

Creates a new accessor for use with Managed Blockchain Ethereum nodes. An accessor object is a container that has the information required for token based access to your Ethereum nodes.

Request Syntax

POST /accessors HTTP/1.1 Content-type: application/json { "AccessorType": "string", "ClientRequestToken": "string" }

URI Request Parameters

The request does not use any URI parameters.

Request Body

The request accepts the following data in JSON format.


The type of accessor.


Currently accessor type is restricted to BILLING_TOKEN.

Type: String


Required: Yes


This is a unique, case-sensitive identifier that you provide to ensure the idempotency of the operation. An idempotent operation completes no more than once. This identifier is required only if you make a service request directly using an HTTP client. It is generated automatically if you use an AWS SDK or the AWS AWS CLI.

Type: String

Length Constraints: Minimum length of 1. Maximum length of 64.

Required: Yes

Response Syntax

HTTP/1.1 200 Content-type: application/json { "AccessorId": "string", "BillingToken": "string" }

Response Elements

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.


The unique identifier of the accessor.

Type: String

Length Constraints: Minimum length of 1. Maximum length of 32.


The billing token is a property of the Accessor. Use this token to make Ethereum API calls to your Ethereum node. The billing token is used to track your accessor object for billing Ethereum API requests made to your Ethereum nodes.

Type: String

Length Constraints: Fixed length of 42.


For information about the errors that are common to all actions, see Common Errors.


You don't have sufficient access to perform this action.

HTTP Status Code: 403


The request processing has failed because of an unknown error, exception or failure.

HTTP Status Code: 500


The action or operation requested is invalid. Verify that the action is typed correctly.

HTTP Status Code: 400


A resource request is issued for a resource that already exists.

HTTP Status Code: 409


The maximum number of resources of that type already exist. Ensure the resources requested are within the boundaries of the service edition and your account limits.

HTTP Status Code: 429


The request or operation couldn't be performed because a service is throttling requests. The most common source of throttling errors is creating resources that exceed your service limit for this resource type. Request a limit increase or delete unused resources if possible.

HTTP Status Code: 429

See Also

For more information about using this API in one of the language-specific AWS SDKs, see the following: