LogoLogo
Upright PlatformAbout Upright
  • Welcome
  • 💡Background
    • Why net impact?
    • Related frameworks
    • Open access to Upright data
  • 📊Metrics
    • Net impact
    • UN SDG alignment
    • SFDR Principal Adverse Impacts
    • EU taxonomy
  • 🌍Coverage
    • Off-the-shelf coverage
    • Custom coverage
  • 🧮Methodology
    • Net impact
      • Overview of the Upright net impact model
        • Extraction of causal links from scientific literature
        • Generalization of scientific knowledge
        • Allocation of impact across value chains
        • Estimation of company product mixes
      • Weighting of impacts
        • IOOI analysis -based monetization
        • Market-price-based monetization
        • Opportunity-cost-based monetization
      • Illustrative example in a simplified economy
        • Appendix: Primer in hierarchical Bayesian inference and Poisson-Gamma models
      • Data sources
    • UN SDG alignment
    • SFDR Principal Adverse Impacts
    • EU taxonomy
    • CSRD Double materiality
  • 📅Releases
    • Release cycle
    • Release notes
      • 1.8.0 (04 / 2025)
      • 1.7.0 (11 / 2024)
      • 1.6.0 (09 / 2024)
      • 1.5.0 (06 / 2024)
      • 1.4.0 (03 / 2024)
      • 1.3.0 (12 / 2023)
      • 1.2.0 (09 / 2023)
      • 1.1.0 (06 / 2023)
      • 1.0.0 (04 / 2023)
      • 0.8.0 (03 / 2023)
      • 0.7.100 (01 / 2023)
      • 0.7.0 (12 / 2022)
      • 0.6.0 (10 / 2022)
      • 0.5.0 (06 / 2022)
      • 0.4.0 (03 / 2022)
  • 💻API
    • Authentication
    • API reference
  • 📗Appendix
    • The Upright net impact framework
    • Illustrative example of attribute-only-once
    • Differences of net impact results and company disclosures
    • Indicative guidelines for classifying investments in line with SFDR
      • Example description of DNSH in pre-contractual disclosures
      • Example description of net impact metrics based indicators in pre-contractual disclosures
      • Old Indicative guidelines for SFDR classification using classic scores
    • Upright data notice
    • NFRD status metadata
    • Communicating Upright's data – Corporates
    • Communicating Upright's data – Investors
Powered by GitBook
On this page
  • Creating a personal access token
  • Obtaining machine user access tokens
  • Sending authenticated requests

Was this helpful?

  1. API

Authentication

Previous0.4.0 (03 / 2022)NextThe Upright net impact framework

Last updated 2 years ago

Was this helpful?

The Upright API supports only Access Token -based authentication. The authentication token must be included in the Authorization HTTP header.

Creating a personal access token

You can create an access token for API usage on your .

You must be logged in, and have access to the API feature enabled in order to access the administration page. If you have trouble accessing the page, please contact your Upright contact person.

Tokens remain valid until you reset them, which you can also do on the administration page.

Obtaining machine user access tokens

If you prefer to setup a machine user in favor of using personal access tokens, contact your Upright contact person. Include the desired email address for the machine user. Note that the email address may not be in use by another user.

Sending authenticated requests

The access token must be included in the Authorization header. The following examples show how to make an authenticated request to the /metrics/legend endpoint.

curl -H 'Authorization: YOUR_ACCESS_TOKEN' <https://api.uprightproject/v1/metrics/legend>
import requests
url = ‘<https://api.uprightproject.com/v1/metrics/legend’>
headers = {‘Authorization’, ‘Bearer {token}’.format(token=YOUR_ACCESS_TOKEN)}
res = requests.post(url, data=data, headers=headers)
print(json.loads(res.text))
import fetch from ‘node-fetch’;
async function run_script() {
  const url = `/metrics/legend`;
  const options = { headers: {‘Authorization’, `Bearer YOUR_ACCESS_TOKEN`} };
  const response = await fetch(url, options); console.log(response.json());
}
await run_script();

For simplicity, the code examples below include the access token as part of the source code. This approach is not recommended in real applications.

💻
administration page