Getty Images API Forums

Authentication (OAuth, CreateSession, Tokens)

RSS Feed

Developer Inactive

  1. I'm trying to make this request (with #### as placeholders)

    curl -XPOST -H 'Content-Type: application/x-www-form-urlencoded' -d 'client_id=#######&client_secret=#######&grant_type=password&username=######&password=######' 'https://api.gettyimages.com/oauth2/token/'

    and i'm getting

    `<h1>Developer Inactive</h1>

    Message edited by Juan Caldera 2 weeks ago

  2. Juan Caldera3 weeks ago

    where username = ESP email and password = ESP password

  3. Juan Caldera3 weeks ago

    where username = ESP email and password = ESP password

  4. Rob Anton-Erik3 weeks ago

    You also need to include your API Key in the request. Please see http://developers.gettyimages.com/api/docs/v3/api-overview.html#authentication

  5. Juan Caldera2 weeks ago

    nope. still broken

    ```curl -XPOST -H 'Api-Key:#####' -H 'Content-Type: application/x-www-form-urlencoded' -d 'client_id=hr3gvgm4htatgudky84hnd49&client_secret=#######&grant_type=password&username=#####&password=######' 'https://api.gettyimages.com/oauth2/token/'````

    i think the password grant doesn't require the api key in the header since it's already in the body.

  6. Mark Pitman2 weeks ago

    You're correct, the Api-Key header is not required when calling the token endpoint. Is your end goal to use the ESP API? If so, you'd need an ESP key generated for you. I can find someone to get in touch with you if that's the case.

    The reason your current key isn't working is because of an outage Mashery had earlier today that seems to have left a number of sandbox keys in a state of limbo. Try creating a new sandbox key. I'll remove the bad ones.

  7. Mark Pitman2 weeks ago

    Someone will be contacting you via email soon.

[ Page 1 of 1 ]