Onboarding
CME Term SOFR API uses OAuth, an open protocol that supports secure authorization in a simple, standard method and decouples authentication from authorization. See also: More details about OAuth API ID authorization and authentication are available in Client API Service Adoption using OAuth 2.0 Protocol
Authorization and Entitlement
A registeredComplete the step(s) that are applicable to your account:
New Clients
Clients with Existing CME Group Logins
After creating and activating a CME Group Login ID, login to CME Customer Center under My Profile and create an OAuth API ID.
Login to CME Customer Center and under My Profile create an OAuth API ID.
.
To access the CME Term SOFR API, client API IDs must be entitled. Request access from the CME Group Market Data API self-service onboarding page or contact Global Account Management (GAM). Testing
Testing and Certification
Certification for CME Term SOFR API is not required.
Access CME Term SOFR API
To access theAvailability
The CME Term SOFR API endpoints in the Production environment, an OAuth API ID and access token are required.
OAuth 2.0 Authorization Server Access Token Retrieval Endpoints
The below OAuth 2.0 authorization server endpoint is available to request and refresh access tokens in the Production environment:
Detail | Production |
---|---|
OAuth Token Endpoint | https://auth.cmegroup.com/as/token.oauth2 |
Info |
---|
Tokens will expire after 30 minutes. |
is available 24 hours a day, 7 days a week. Clients systems should consider all returned data to be accurate at the time of the request submission.
The latest rates will publish and be available around 10:00 AM UTC.
Accessing CME Term SOFR API
This section describes the message specifications and URLs to access CME Term SOFR API.
CME Term SOFR API URLs
Below are the base URLs to access the CME Term SOFR API endpoints:
Environment | Base URL |
---|---|
Production | https://markets.api.cmegroup.com/term-sofr-rates/v1 |
The CME Term SOFR API is available 24 hours a day, 7 days a week. Clients systems should consider all returned data to be accurate at the time of the request submission.
The latest rates will publish and be available around 10:00 AM UTC.
Message Specifications
The business message specifications for CME Term SOFR API are available below.
The Path value, prefixed with Base URL, will be a specific end point for the HTTPS GET request.
Each HTTPS GET call must have the header parameter "Authorization" with value "Bearer" pre-pended to the OAuth token (including a space separator).
example: "Bearer <Oauth Access token>"
Name | Path | Method | Description |
---|---|---|---|
/latest | GET | Gets the Latest Term SOFR Rates for the current date. By default returns the Latest Term SOFR rates for all four products. Accepts the below requests/inputs:
| |
/history | GET | Gets historical Term SOFR rates based on a single date or range of dates provided by the customer. By default returns all historical Term SOFR rates. Accepts the below requests/inputs:
|
Pagination
To make responses more manageable, CME Term SOFR API returns results in pages.
The metadata "type" will return page.
By default, 1000 results per page are included, displayed results per page can be requested (up to 2000) using the pagesize parameter.
CME Term SOFR API also supports a pagenumber parameter to allow clients to view a specific page in the result set.
If pagination (page and size values) is passed in the URL explicitly, then the same will be used to retrieve data.
Name
Description
Additional Details
pagesize
Number of results returned per page
Optional query parameter.
The maximum size value is 2000 and the minimum size value is 1.
If size is not specified, the default is 1000.
If size is specified but is less than 1 (e.g., size=0 or size=-9 ), the default of 1000 is used.
Response Metadata fields
The following information describes the metadata JSON element on the response payload to client systems.
Field | Description | Usage |
---|---|---|
pageSize | Maximum number of data elements in the JSON result set or page. | Defaults to 1000 with a maximum of 2000. Can be used as a query parameter to limit the number of elements returned per request. E.g. /history?pageSize=500 |
totalPages | Total number of pages in the full result set. |
|
pageNumber | The current page in the set of pages. | If totalPages is greater than 1, pageNumber is used to navigate to the next page of the result set. E.g. /history?pageNumber=2 (retrieve the second page in the data set) |
totalElements | Value indicates the total Elements in the full data set. |
|
type | Type of JSON data set | Always set to value “page” |
elementsInReponse | Number of data elements in the JSON result set or page. |
|
Contact Information
For production requests, contact the Global Command Center (GCC).
For other inquiries, contact Global Account Management (GAM).