Quick Converter: V 1.0 to V2.0

Introduction

The purpose of this document is to help users convert from Pulsar’s GraphQL V1.0 to GraphQL V2.0. The document aims to cover the following:

• Necessary changes in endpoints

• Necessary changes in field types/names

• Necessary changes in variable types/names

• Required/Non-Required Parameter changes

There are plenty of things that have remained unchanged across the two versions of the GraphQL API. They include but are not limited to:

• Your token: the bearer token you use to access the graphQL is the same.

• Your search hashes/profile IDs: the search hashes and profile IDs remain the same.

• The data limitations: the limitations that existed for the prior version of the API are still in place.

CORE Call Conversion

This section is true for all calls made to the former CORE endpoint.

Things to Change:

• The Endpoint

  • Old Endpoint: data-explorer.pulsarplatform.com/graphql/core

  • New Endpoint: data.pulsarplatform.com/graphql/core

TRAC Search Call Conversion

This should be used for any calls looking for top level search data, or a list of searches. For example this call from v1.0 would now be done on this endpoint.

Things to Change:

• The Endpoint

  • Old Endpoint: data-explorer.pulsarplatform.com/graphql/trac

  • New Endpoint: trac.pulsarplatform.com/graphql

• Subfields

  • Searches.search{} -> Searches.nodes{}

    • Consult the schema to see the subfields available under nodes

• Variables

  • “limit” -> gone!

  • “page” -> gone!

TRAC Data Call Conversion

This should be used for any calls looking for results from TRAC. For example this call from v1.0 would now be done on this endpoint.

Things to Change:

• The Endpoint

  • Old Endpoint: data-explorer.pulsarplatform.com/graphql/trac

  • New Endpoint: data.pulsarplatform.com/graphql/trac

• Variable Types

  • Filter! -> FilterInput!

  • Option -> ResultsOptionsInput

• Variables

  • “stat” -> gone!

  • “dimension” -> gone!

  • “searches” -> “searchIds”