Quote Summary
At this step, the creation of Quote ID, Opportunity ID, and quote takes place
These unique identifiers serve as strategic enablers, helping SPs to drive the rest of the Ordering API phases. The Opportunity ID is created when the SP has an opportunity to do business with an end customer and initiated the process with them. By associating a Quote ID with a particular product configuration that includes a Price Offer (Access, Port, Installation, Discount Range, Available Promotions), SPs will be able to maintain/record their discussions. It ensures alignment between both parties on offerings, rates, promotions, and discounts. Beyond the IDs, recording of configuration details—product options, access speeds, port speeds, billing preferences, sites and more—ensures seamless execution.
Security
This RESTful service uses a client id enforcement policy as the authentication mechanism. Please work with the Client On-Boarding Team if you do not have the necessary credentials.
Endpoints and Headers
Opportunity Quote POST
Environment | Base URI |
UAT | https://uat-att-pricequote-eapi.nprd-gw.cloud.att.com/api/v1/opportunity-quote |
Production | https://att-pricequote-eapi.gw.cloud.att.com/api/v1/opportunity-quote |
Site POST
Environment | Base URI |
UAT | https://uat-att-pricequote-eapi.nprd-gw.cloud.att.com/api/v1/site |
Production |
Config AIAB POST
Environment | Base URI |
UAT | https://uat-att-pricequote-eapi.nprd-gw.cloud.att.com/api/v1/config/aiab |
Production | https://att-pricequote-eapi.gw.cloud.att.com/api/v1/ config/aiab |
If you are a Connector, meaning you develop on behalf of multiple Solution Provider accounts to retrieve information for them, you will use the same URL and ensure that you pass the unique client header per Solution Provider.
API Headers
The following are the fields in the request headers of the Quote API.
Field Name | Field Description | Mandatory/Optional |
content-type | Application/json | M |
accept | Specifies the format of the response message body. Structured text message payloads are required to support application/json. No other format is permitted. As they are the only supported format, the accept header is not relevant for those requests.
| O |
x-trace-id | This field is used for passing a trace ID between API hops for end-to-end traceability.
| M |
x-transaction-id | This field is used for passing a traceable ID to uniquely identify the transactions.
| O |
client_id | This field represents the client id. | M |
client_secret | This field represents the client secret. | M |
source | This field should identify the calling system/application.
| O |