CMR Environments Table
CMR Environment | Base API URL (through ECHO) | Associated URS Environment |
---|---|---|
Operational (OPS) | ||
Acceptance Test (UAT) | ||
Systems Integration Test (SIT) |
curl -X POST --header "Content-Type: application/xml" -d "<token><username>sample_username</username><password>sample-password</password><client_id>client_name_of_your_choosing</client_id><user_ip_address>your_origin_ip_address</user_ip_address> <provider>PROV_ID</provider></token>" https: //api.echo.nasa.gov/echo-rest/tokens |
The <provider> element in blue in the example above is only used if you are planning on working as or 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.
Another way using curl if you don't want to escape any characters, you can use the "file input" option to create a file that looks like the following:
mytokengenerator.xml
< token > < username >sample_username</ username > < password >sample-password</ password > < client_id >client_name_of_your_choosing</ client_id > < user_ip_address >your_origin_ip_address</ user_ip_address > < provider >PROV_ID</ provider > </ token > |
Then, the full curl command looks a little bit different:
curl -X POST --header "Content-Type: application/xml" -d @mytokengenerator .xml https: //api-test.echo.nasa.gov/echo-rest/tokens |
Again, if using a programming language, just place the curl example parts into the correct http message header or body locations.
A sample response from the curl call is:
<? xml version = "1.0" encoding = "UTF-8" ?> < 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 > < provider >PROV_ID</ provider > </ token > |