Back to all updates

almost 3 years ago

One month left + Bonus Tech Tip: Authorization

There’s one month remaining in the Hack the Journey Online Edition hackathon! Submissions are due July 29 before 5:45pm EDT (11:45pm CEST).

Start your submission now

Starting a submission is a good way to make sure that your app meets the requirements. There’s nothing worse than getting to the deadline, only to realize that you’re missing a key component. Remember: once you submit a project, you can keep editing it, as needed, at any time prior to the submission deadline. Need a primer on how the submission form works? Head over to our submission form tutorial.

Remember the Requirements

Don’t forget: It is mandatory that you provide a way to access your solution in order to build, deploy and test it (i.e. a link to your GitHub Repository). Your solution will likely be open source, but if it is a private repository, we will still need access to test it such as giving log-in credentials or adding permissions to a specific testing account.

Be sure to review the rest of the rules and verify eligibility and technical requirements have been met!

Bonus Tech Tip: Authorization for Amadeus APIs

OAuth is a protocol that enables a token-based workflow, which is more secure than basic authentication. It provides a way to ensure that a specific user has permissions to access services and resources.

OAuth uses access tokens for accessing APIs. A token represents a permission granted to a client to access some protected resources. The method to acquire a token is called grant.

There are different types of OAuth grants. Amadeus for Developers uses the Client Credentials Grant.

To request an access token you need to send a POST request with the following body parameters to the authorization server:

  • grant_type with the value client_credentials
  • client_id with your API Key
  • client_secret with your API Secret

Both API Key and API Secret were provided to you when you created your application in the portal.

The authorization server will respond with a JSON object containing the following properties:

type set to amadeusOAuth2Token string

username your username (email address)

application_name the name of your application

client_id your API Key (same as the one used in the request)

token_type with the value Bearer

access_token your authorization token

expires_in an integer representing the expiration time (in seconds) of the given token

state with the value approved

You can get a new token through efforts including:

  1. cURL
  2. Ruby
  3. Amadeus SDKs

To get more information on Authorization for Amadeus APIs, including examples of token requests, check out the full Authorization Guide

Questions?

If you have any questions about the hackathon, please post on the discussion forum.