An overview of the differences between the Customer Origins and the Origins API is provided below.
API | TLS |
Functions |
Dedicated Origin Entry Endpoints |
---|---|---|---|
Customer Origins API |
|
|
|
Origins API |
|
|
|
The Customer Origins API, which is our initial API implementation, does not support managing a customer origin group's TLS configuration. It also does not support the retrieval of the Function@Edge functions associated with your customer origin groups. Finally, it requires that you manage a customer origin and all of its entries within a single request. For example, you can create a customer origin group and all of its origin entries through the Add Customer Origin endpoint.
The Origins API, which is our latest implementation, uses dedicated endpoints to manage a customer origin group and origin entries. For example, setting up a customer origin group consists of requesting the following endpoints:
Additionally, it allows you to retrieve the Function@Edge functions associated with your customer origin groups.
The following endpoints automate the administration of customer origin configurations.
Task | Endpoint |
---|---|
Add |
Add a customer origin through |
Delete |
The Delete Customer Origin endpoint deletes the specified customer origin configuration. |
Get |
Retrieve a list of customer origin configurations through
Retrieve a specific customer origin configuration through Retrieves the propagation status for a customer origin configuration through the Get Customer Origin Status endpoint. |
Retrieve a list of the IP blocks used by our CDN service. |
|
Get Origin Shield Locations |
Retrieve a list of Origin Shield locations through these platform-specific endpoints: |
ADN Gateway Reselection |
The Reselect ADN Gateway endpoint updates the failover list of ADN Gateway servers for the specified customer origin configuration. |
Update |
Update a specific customer origin configuration through |
This section describes endpoints in the mcc service.