Skip to content

API Accreditation Process ​

How to activate the service

To find out how to activate the service, please contact your Account Manager.

This page describes what you get once activation is complete and how to start working with the APIs.

In brief (TL;DR) ​

  1. Developer profile: sign in with your profile at account.gipo.it. With the Developer role active, you see the configuration menus.
  2. OAuth App: in the Developer area you find your OAuth application, with its client_id and client_secret.
  3. Data Access: use your OAuth client data along with login credentials on a specific tenant to obtain tokens and perform API operations.

Integration Roadmap ​

Phase 1: Developer profile ​

The developer profile is your starting point for configuring the integration.

  • Sign in: log in at account.gipo.it with your account.
  • Developer Role: with the role active, you see the Developer menus. If you don't see them, contact your Account Manager.

Phase 2: OAuth application ​

From your developer profile you manage your technical solution:

  1. Go to Developer > OAuth Applications on account.gipo.it.
  2. Configuration: here you find the app name, Redirect URIs (HTTPS), and enabled scopes (e.g., patients, agendas, medical reports).
  3. Environment Management:
    • Recommended: use two separate Apps (e.g., "MyApp - Test" and "MyApp - Prod") to separately manage client_secret and different redirects between your development and production environments.
    • Alternative: you can use a single App if your architecture allows for dynamic flow management across multiple environments.
  4. Credentials: each app has its own client_id and client_secret.

Phase 3: Accessing Data (Operations) ​

To call the APIs and access clinical data, you need a login account on a tenant.

  • Medical Center account: the Medical Center creates a technical account dedicated to the integrator (e.g., integration.name@center.it) directly from its own management system, under Configurazione → Permessi → Utenti (www.giponext.it/utenti), choosing the most suitable role for the integration (administrator or doctor, with no constraints). No support ticket is needed. Once created, you will use these credentials in your application's OAuth login popup to access the center's real data.

🛠️ Technical Checklist ​

  • [ ] Active account on account.gipo.it with Developer role.
  • [ ] Redirect URI correctly configured (HTTPS).
  • [ ] Login account created by the Medical Center.
  • [ ] client_id and client_secret available.

Useful Resources:Registration Guide ➡️ | OAuth Flow Details ➡️

🆘 Common Questions ​

  • Why can't I see the data? App credentials (Phase 2) identify your software, but data access (Phase 3) requires a valid Medical Center account.
  • Can I change Redirect URIs later? Yes. You can edit the app configuration (including Redirect URIs) yourself from the account.gipo.it portal, without contacting support. Some changes may need to be reviewed again before they take effect.
  • Are the credentials expired? Remember that the client_secret must be stored securely and should never be exposed in client-side (frontend) code.

Next steps ​