Accessing the API
Optimization
(GET | POST | PUT | DELETE) https://optimization-api.rigor.com/{version}/{Path}
Monitoring
(GET | POST | PUT | DELETE) https://monitoring-api.rigor.com/{version)/{Path}
Supported Methods
Rigor utilizes a versioning scheme in the API url to preserve backward compatibility for our clients.
Authentication
All API access is authenticated via an API token sent in the HTTP header with each API request. Your API token is available in your Optimization and Monitoring Account Settings.
Supply a header named API-KEY in your API requests to pass your API User Key value. For example:
API-KEY: 6DE1B93D4419EE2A7B81173A453FCFF8
If your Optimization API user key has multi-account access, you may also need to supply a header named ACCOUNT-KEY for any API functions that operate on a single account (eg. Tests, Snapshots, Defects, Content). Your API token is available in your Optimization Account Settings.
If your Monitoring API has mutl-account access there is a unique API per account that you'll need to use.
Content Format
Content can be sent or received in either JSON or XML. By default, all content is returned in JSON.
For POST and PUT operations, you must set the Content-Type header to either application/json or application/xml. For example:
Content-Type: application/json
To receive in a different format, use the Accept header, for example:
Accept: application/xml