> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/digital-river-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalriver.com/digital-river-api/general-resources/standards-and-certifications/integration-checklists/admin-portal.md).

# Admin portal

The [checklist items](#integration-checklist) and [standards](#integration-standards) in this section relate to the admin portal you must provide with your integrated tool. Using this portal, you should be able to configure the API keys for every client instance. During each [end site implementation](/digital-river-api/general-resources/standards-and-certifications/certification-process.md#end-site-implementations), you use this portal to set the client-specific API keys and perform other configurations.

## Integration checklist <a href="#integration-checklist" id="integration-checklist"></a>

Click any checklist item to provide more detail on how to meet the integration standard.

* [ ] ​[Do you provide an admin portal to configure secret and public Digital River API keys?​](#configuring-secret-and-public-digital-river-api-keys)
* [ ] [Do you provide an admin portal to configure a single default ship-from address?](#configuring-a-single-default-ship-from-address)

## Integration standards

These integration standards relate to building an admin interface:

### Configuring public and confidential keys <a href="#configuring-secret-and-public-digital-river-api-keys" id="configuring-secret-and-public-digital-river-api-keys"></a>

You must provide a utility in your platform's admin backend portal to assign [public and confidential API keys](https://docs.digitalriver.com/digital-river-api-reference/digital-river-api-reference-guide/api-structure). These keys then determine which Digital River account is used within the store. Each store must be given its own set of public and confidential keys.

### Configuring a single, default ship from address <a href="#configuring-a-single-default-ship-from-address" id="configuring-a-single-default-ship-from-address"></a>

You must provide a utility in your platform's admin backend portal to assign a default [ship-from address](/digital-river-api/integration-options/checkouts/creating-checkouts/providing-address-information.md#ship-from-address). The default address might represent, for example, the designated warehouse of the storefront. Each client can have more than one ship-from address. However, only one should be designated as the default.

Digital River uses the default address you provide to [calculate regional and localized taxes](/digital-river-api/integration-options/checkouts/creating-checkouts/tax-calculations.md), [fees](/digital-river-api/product-management/regulatory-fees.md), and regulations during checkout.‌

## API interfaces <a href="#api-interfaces" id="api-interfaces"></a>

| Documentation                                                                                           | Direct API                                                                                                              | PHP SDK                                                                                                                  |
| ------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| [​Country specs​](/digital-river-api/integration-options/checkouts/creating-checkouts/country-specs.md) | ​[Country specifications​](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/country-specifications) | ​[CountrySpecification](https://github.com/DigitalRiver/digital-river-php/blob/main/docs/Model/CountrySpecification.md)​ |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digitalriver.com/digital-river-api/general-resources/standards-and-certifications/integration-checklists/admin-portal.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.