Link API
Bounce Link RESTful Web API documentation
Last updated
Was this helpful?
Bounce Link RESTful Web API documentation
Last updated
Was this helpful?
The Link API provides methods for interacting with Link phygital tags, verifying authenticity and ownership of connected collectibles, and managing their claim state.
For details on API authentication, limits and environments see
Link API interaction flow to validate and claim a Bounce Link tag.
GET
Link tag statusGET
https://api.letsbounce.gg/v1/link/status/{batch_id}/{tag_id}
This endpoint returns the status of a single Bounce Link tag by the tag's ID in the specified batch.
batch_id*
Number
tag_id*
Numbrt
Link Tag status response:
GET
Link tag status (batch)GET
https://api.letsbounce.gg/v1/link/status/{batch_id}
This endpoint returns the status of a list of Bounce Link tags by an ID range in a specified batch.
batch_id*
Number
Link tag batch ID
offset
Number
query offset
count
Number
batch query size
Link Tag batch status response:
POST
Validate a Link Tag tap (by code)POST
https://api.letsbounce.gg/v1/link/validate/code
In addition to an origin check, this can be used to pass tag verifiable details to a custom hosted page that is redirected to by a Bounce Link Tag tap.
Use this API to generate a short-lived claimCode
to use for claiming a Link phygital via the API.
code*
String
Short-lived validation code
If a code is valid
, tag details will be available in the response.
If a tag is open for claim (unclaimed), a claimCode
will be provided that you can use to trigger a claim with the Link API.
Link Tag tap validation response:
POST
Validate a Link Tag tap (by tag params)POST
https://api.letsbounce.gg/v1/link/validate/tap
This endpoint can be used to validate the authenticity, currentness and validity (non-expiry) of a Link tag tap based on parameters received directly from the tag's dynamic URL.
Rather than extracting the URL params one-by-one, you may provide the entire URL of your claim page, including all dynamic parameters, and these will be parsed on the server.
The tag's batch ID and tag ID may be available as route params in the URL, and must be provided if they are (depending on project setup).
Use this API to generate a short-lived claimCode
to use for claiming a Link phygital via the API.
url*
String
project_id*
String
If a code is valid
, tag details will be available in the response.
If a tag is open for claim (unclaimed), a claimCode
will be provided that you can use to trigger a claim with the Link API.
Link Tag tap validation response:
POST
Claim a Link TagGET
https://api.letsbounce.gg/v1/link/claim
User accounts can be either an Ethereum-compatible wallet addresses, or OAuth-compatible user IDs.
If a wallet is provided, it must be a string formatted hex with a 0x
prefix. For example: 0xb794f5ea0ba39494ce839613fffba74279579268
. Non-EVM wallets are currently not supported by the API.
Please contact the team at support@letsbounce.gg for OAuth app integration or non-EVM wallet claims.
claimCode*
String
A valid claim code from a validation response
user_account
String
A user's OAuth shared identifier
user_wallet
String
A user's Ethereum wallet address
In most cases claims are instant and a claim attempt will return as completed.
However, in some cases (and some blockchains), a claim might take longer than the request window, and a pending state will be returned.
In that case, please follow up on the claim request with a claim status request using the provided claimId
Link Tag claim response:
GET
Link Tag claim statusGET
https://api.letsbounce.gg/v1/link/claim/status/{claim_id}
This endpoint can be used in cases where a claim request is long-running, or to verify the status of a claim request by claimId
.
claim_id*
String
Link Tag claim status response:
This endpoint can be used to validate the authenticity, currentness and validity (non-expiry) of a Link tap based on a code received from a redirection or deep-link.
This endpoint can be used to claim an asset to a user account using a claimCode received from either a or Link API calls.
The will manage delayed claims automatically and pull for status updates until a claim succeeds or fails.
A claim ID received by a API call