Page History
...
CMR Environment | Base API URL (through ECHO) | Associated Earthdata Login (URS) Environment |
---|---|---|
Operational (OPS) | ||
User Acceptance Test (UAT) | https://api-test.echocmr.uat.earthdata.nasa.gov | https://betauat.urs.eosdisearthdata.nasa.gov |
Systems Integration Test (SIT) | https://testbedcmr.sit.echoearthdata.nasa.gov | https://alphasit.urs.eosdisearthdata.nasa.gov |
2. On a terminal window execute the curl command for the environment you selected.
Infotip | ||
---|---|---|
| ||
|
Note:
- Depending on the environment you selected, the Base API URL may be different from the example. If so, replace the purple text with the correct Base API URL.
- If you are embedding the token REST messages into a programming language, create an HTTP message and place the same components from the curl example into either the message header or body.
- The <provider> element in blue in the example above is only used if you are planning on working on behalf of a data provider (ingesting). Client developers (searching) can leave it out.
- If you have special characters in your password, you will probably need to escape them using a backslash.
...
If you don't want to escape any characters, but still want to use curl - implement the "file input" option to create a file that looks like the following:
...
Tip | ||
---|---|---|
| ||
<token> |
...
...
...
...
Note: mytokengenerator.xml
...
can be used as a file name, which simplifies the command.
...
See example underneath step 2 for original command and the example below for simplified command.
...
Tip | ||
---|---|---|
| ||
|
...
|
...
|
...
...
...
...
title | Example |
---|
<?xmlversion="1.0"encoding="UTF-8"?>
<
token
>
<token>
<id>75E5CEBE
...
-6BBB-2FB5-A613-0368A361D0B6</
...
id>
<username>sample
...
_username</
...
username>
<client_id>client
...
_name_of_your_choosing</client_
...
id>
<user
...
_ip_
...
address>your_origin_ip_address</user_ip_
...
address>
...
<
...
</
token
>
...
/token>