Skip to main content

Introduction

Overview of Graph API​

The Graph API is the primary way to get data into and out of the Vryno platform. It's an HTTP-based API that apps can use to programmatically query data and perform a wide variety of other tasks.

The Graph API is named after the idea of a "social graph" — a representation of the information on Facebook. It's composed of nodes, edges, and fields. Typically you use nodes to get data about a specific object, use edges to get collections of objects on a single object, and use fields to get data about a single object or each object in a collection. Throughout our documentation, we may refer to both a node and edge as an "endpoint". For example, "send a GET request to the User endpoint".

HTTP​

All data transfers conform to HTTP/1.1, and all endpoints require HTTPS. Because the Graph API is HTTP-based, it works with any language that has an HTTP library, such as cURL and urllib. This means you can use the Graph API directly in your browser. For example, requesting this URL in your browser...

----website

... is equivalent to performing this cURL request:

curl -i -X GET "https://graph.facebook.com/facebook/picture?redirect=false"

HTTP Status Codes and Error Types​

LinkedIn uses 'https://www.rfc-editor.org/rfc/rfc2616#section-10' for each API’s response.

Status codes are divided into the following five categories:

  • 1xx: Informational - Communicates transfer protocol-level information.
  • 2xx: Success - The request was successful.
  • 3xx: Redirection - The client must take some additional action to complete the request.
  • 4xx: Client Error - Failed request due to client error.
  • 5xx: Server Error - Failed request due to server error.

- 400 Bad Request​

A 400 Bad Request error means that the server was unable to proceed with the request. The most common cause of the error is bad syntax in the request URL or body. To fix a 400 Bad Request error, do the following:

- 401 Unauthorized​

401 Unauthorized errors are usually caused by a problem in the request header of your API call. For example, if you don't use a valid access token when you make an API call on behalf of a LinkedIn member, a 401 Unauthorized error is returned. Some common cases are:

Error TypeFix
Unknown authentication schemaUnrecognized authentication header schema. Make sure the authentication header follows the format Authorization: Bearer (your access token)
Empty OAuth2 access tokenThe authentication header is missing or empty. Make sure the authentication header follows the format Authorization: Bearer (your access token)
Invalid access tokenIncorrect access token, make sure you follow the 'https://learn.microsoft.com/en-us/linkedin/shared/authentication/authentication' to get a correct access token.
Expired access tokenThe access token has expired, see how to 'https://learn.microsoft.com/en-us/linkedin/shared/authentication/authorization-code-flow?tabs=HTTPS1'
The token has been revokedThe access token has been revoked by the member from their privacy settings on Vryno’s website. To continue using your application, the member has to re-authenticate to get a new access token for your application.

- 403 Access Denied​

When your application makes an API call with a member’s access token, Vryno checks if the access token has permission to access the API. If the access token does not have the correct permissions, a 403 Access Denied error is returned. When this happens, check the following:

If you continue to see the error, reach out to your partner technical support channel or 'https://developer.vryno.com/support'.

- 404 Resource Not Found​

This error occurs when your application tries to call an API or fetch an entity that does not exist. For example, the API to get a friend’s profile is /v2/people/id={personId}, not /v2/person/id={personId}. In some cases (Ads, for example), a 404 error is returned when attempting to access a restricted API. See '403 Access Denied' and contact your partner technical support channel if you continue to see the error.

- 405 Method Not Allowed​

This error indicates that the HTTP protocol methods in your request are not supported. Check the documentation for the API to see supported methods.

- 411 Length Required​

This error indicates that the server refuses to accept the request without a defined Content-Length header. Please make sure POST requests with an empty body have a Content-Length header specified.

- 429 Rate Limit​

On Vryno's platform, all API requests that you make are rate limited to prevent abuse and to ensure service stability. These errors will return an error message of "Resource level throttle limit for calls to this resource is reached." If you get a 429 Rate Limit error, check if too many redundant calls are being made and review your application’s Usage & Limits in the Developer Portal. If you've confirmed that the current rate limits do not meet your application’s needs, contact us if you are our partner, or join our partner program through https://developer.vryno.com/partner-programs.

- 500 Internal Server Error​

A 500 Internal Server Error indicates that Vryno is experiencing an internal error. If you continue to receive server errors, record the following details and report it to your partner technical support channel or https://developer.vryno.com/support:

  • Request: url, method, header. For example, access_token, body.
  • Response: header. For example, x-li-uuid, x-li-fabric, x-li-request-id, body.
  • Your application configuration. For example, Client ID.

- 504 Gateway Timeout​

A 504 Gateway Timeout error happens when it takes too long for LinkedIn to process your API call. Due to the nature of cloud APIs, LinkedIn's services may be occasionally interrupted or temporarily unavailable for reasons outside of its control. Make sure you have proper error handling logic, such as caching and retry patterns, to cover these issues. If your application continues to receive these errors, contact https://developer.vryno.com/support to report the issue.

Host URL​

Almost all requests are passed to the https://test1ms.vryno.dev/api/graphql/crm host URL.