On the backend of the application, a developer has written code that will use basic authentication to confirm that your account has authorization to the data you will access from the application.
The developer documentation for basic authorization can be found here. There are two types of Basic Authentication over HTTPS that developers can use- private and public.
Private authentication should be used in secure environments, such as a server side application. You can see examples of this type of authentication in shell and curl in the documentation page. In this type of authentication you'll pass both your API username and API password in the headers of your API call.
If you are unfamiliar with this type of authentication, you'll want to check out some of the Intrinio SDKs on Github (API v2). You can filter by the coding language of your choice and then dig into the code to see how other developers are using their API credentials to authenticate.
In these instances, you should use public key authentication. Public authentication differs from private authentication in that you only pass a single public key in your header, rather than an API username and password. You must also specify the domains where your public key should work.
Getting Your Keys For Authentication
You can create a free account at intrinio.com/login. When you do, you'll see this section on your account page:
System generated API keys will be present when you sign up and you can create more keys by clicking "Add New Key". When you do, you'll be prompted to create either a public key or a private key. Notice how the public key includes just one key while the private keys include two, a username and a password.
The public key includes an option to specify the domains where it will be valid whereas the private key allows for "collaborators".