Access Red Rover data via this REST API for Organizations that have granted you access. # Authentication The API is protected by HTTP Basic Authentication. Each application that connects to the API has a unique username and password that it must supply with every request. This value needs to be supplied as an HTTP Header: `Authorization=BASIC [hash]`. The value of [hash] is the string username:password base64 encoded. Endpoints marked for Basic Auth can be used with the Basic Auth username and password that you have been assigned. # API Information ## Api Key Each Red Rover organization that has authorized your application has a unique API Key for your application. To retrieve the API Key, you can use the Organization endpoint (`api/v1/organization`) which returns an ApiKey uniquely used for each Organization. You must supply this as an HTTP Header when accessing that organization: `apiKey=[apiKey]`. The domains that require this `ApiKey` header are labeled as 'Requires an ApiKey'. ## Identifier Where an `Identifier` can be specified in the route, you may either supply the Red Rover Id of the object (numeric) or the External Id (alpha-numeric). When specifying an External Id, you will need to prepend the External Id with the pipe character`|` (e.g. `|ABC123`). Please note that this is only the case when the External Id is within the route. If the External Id is contained within the body of the request, do not append the pipe character. ## Rate Limiting Requests are rate limited at a default rate of 100 requests per minute ## Transaction Id Each request can be supplied with a `TransactionId` GUID which will be logged with the request. The `Transaction Id` can be supplied as an HTTP Header: `TransactionId=[transactionId]`. If no `Transaction Id` is supplied, one will be generated for you. Please use a distinct TransactionId for each request.
1 maintainer
Metadata
1 maintainer
Release files for redrover-api 1.14.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| redrover_api-1.14.0.tar.gz | 186.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| redrover_api-1.14.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 510.7 kB
Release files / redrover_api-1.14.0.tar.gz
| Download URL | redrover_api-1.14.0.tar.gz |
|---|---|
| Size | 186.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
39757bc5f58b8ea6d4e8614f5f8d8c4c478463ce0a85b637c67e18e514f0c412
|
|
BLAKE2b-256 checksum How to use checksums |
07c6e68f7b6979fa42fc30a93eab228c6c7f88ffbdf0481a7f2508e6532cbb5c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.6
|
Release files / redrover_api-1.14.0-py3-none-any.whl
| Download URL | redrover_api-1.14.0-py3-none-any.whl |
|---|---|
| Size | 324.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f4b8b751fde652ad6d2fe4e05ae389f5e9f23a2bd8d0bc78cedf9f99c25bd028
|
|
BLAKE2b-256 checksum How to use checksums |
df1898c465d31c90c8f47803357b196fa804866506ec73c2f6ade4fd811dfe81
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.6
|
