Welcome to the Perenso TradeShow API V1 documentation. This guide provides comprehensive information on how to interact with our REST API, authentication methods, and best practices for implementation.Authentication#
OAuth 2.0 Client Credentials#
Use the OAuth 2.0 Client Credentials grant type to authenticate with the REST API. As described in Client Credentials - OAuth 2.0 Simplified, send an HTTP POST message to our Authentication URL.
You will need to specify the following information in the POST request:1.
grant_type – The grant type specifies the authentication flow you will use, and it should go in the body of the POST message with the following format:
grant_type=client_credentials
1.
scope – The scope indicates the type of resource you are requesting access to. The value 100214 means you are requesting access to the REST API. It goes in the body and is combined with other data using an ampersand (&):
1.
client_id – The client ID is the show ID for the show you are hosting. It will be provided to you by Perenso Show Support. This data can be specified in either the body of the request or base64-encoded into the authorization header with the client_secret. If included in the body, combine it with the other data using an ampersand (&):
1.
client_secret – The client secret is an encoded value that acts as a password to authenticate access to the show's API. It is generated by our systems and provided by Perenso Show Support. This data can be specified in either the body of the request or base64-encoded into the authorization header with the client_id. If included in the body, combine it with the other data using an ampersand(&):
Example Authentication Request#
Upon successful authentication, you'll receive an access token and refresh token that you'll use in subsequent API requests.Rate Limiting#
The Perenso TradeShow API implements rate limiting to ensure fair usage and maintain service quality for all users.Rate Limit Details#
Limit: 300 requests per minute per client
Response when limit exceeded: 403 Forbidden
Best Practices#
To avoid hitting rate limits, consider implementing the following strategies in your application:Request Throttling: Implement client-side throttling to stay within the 300 requests per minute limit
Caching: Cache responses where appropriate to reduce the number of API calls
Bulk Operations: Use bulk endpoints when available to create or update multiple records in a single request
Modified Date Filtering: Use the modifiedAfter parameter to only retrieve records that have changed, reducing unnecessary API calls
Exponential Backoff: If you receive a 403 Forbidden response due to rate limiting, implement exponential backoff before retrying
If you consistently require higher rate limits for your use case, please contact Perenso Show Support to discuss your needs.Working with API Resources#
Accessing Specific Records#
When retrieving data from the API, each record will contain a unique identifier in the id field. This identifier can be used to access specific resources directly.
For example, if you receive a list of attendees with the following structure:[
{
"id": "a123456",
"firstName": "John",
"lastName": "Doe",
"email": "[email protected]"
},
{
"id": "b789012",
"firstName": "Jane",
"lastName": "Smith",
"email": "[email protected]"
}
]
You can access a specific attendee by using their unique id in the endpoint path:Retrieving recently modified items#
When querying collections, you can supply a modifiedAfter parameter to only retrieve items that have changed since the specified date:GET /attendee?modifiedAfter=2025-01-31
The modifiedDate field will be included in the response and items will be sorted from most recently modified to least recently modified:[
{
"id": "a123456",
"modifiedDate": "2025-05-07T12:25:00",
"firstName": "John",
"lastName": "Doe",
"email": "[email protected]"
},
{
"id": "b789012",
"modifiedDate": "2025-05-07T12:30:00",
"firstName": "Jane",
"lastName": "Smith",
"email": "[email protected]"
}
]
Sorting#
When querying collections, you can use any field except modifiedDate to sort the data:GET /attendee?sort=attendeeID:asc
Support#
If you encounter any issues with authentication or API usage, please contact Perenso Show Support for assistance. Modified at 2025-10-15 22:17:01