The Rise API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.
Your API Key is used to authenticate requests and identifies your Rise.com account. It should be stored securely: make sure it is kept out of version control, and can only be accessed by those who need it. Treat it like any other password.
All API requests must use Bearer Authentication: your API Key must be provided as a Bearer Token in the
Authorization header. All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.
curl -i https://api.rise.com/users -H "Authorization: Bearer $API_KEY"
All paginated endpoints are cursor-based and return a
nextUrl property. If not
nextUrl indicates that there may be additional results. A
GET request can be made to the
nextUrl URL to get the next page of results. A
null indicates there are no further results. All paginated endpoints support a
limit query string parameter that specifies the maximum number of results to return in a single response. The
limit value must be between 1 and 100 (except where otherwise noted; and defaults to 50 if not specified).
Endpoints Supporting Pagination
A 400 response containing a list of errors will be returned when the request is not valid. Some common error codes include:
validation_failed: The request body has a validation error
missing_api_key: The request is missing an API Key
invalid_api_key: The API Key provided is invalid
"errors" : [
"code" : "invalid_email",
"message" : "\\"email\\" must be a valid email"
All API responses contain an
X-Request-Id header. When contacting support, please include this header for any questions relating to a specific request.