Kavitro GraphQL Reference

website·Indexed 31 days ago

https://kavitro.dev/

Complete GraphQL API reference for Kavitro, including detailed documentation on mutations for updating submissions, projects, contracts, roles, and task bundles, as well as object definitions for edges and connections.

Tokens
209.6K
Snippets
1.3K
Records
2.4K
Agent score
51%

What's inside Kavitro

  1. Overview of the Kavitro API

    The Kavitro API allows developers to programmatically access and update data within a Kavitro account for integration with websites or other applications. The API is built using GraphQL, a flexible query language that allows clients to specify exactly which data fields they need, reducing over-fetching and under-fetching.
  2. Delete a company using the deleteCompany mutation

    The deleteCompany mutation allows for the deletion of a company record. It requires a non-null id of type ID! and returns the Company object that was deleted, which represents information about the company.
    deleteCompany(
      id: ID!
    ): Company
  3. Delete an ordinance type using deleteOrdinanceType mutation

    The deleteOrdinanceType mutation allows you to delete a specific ordinance type. It requires a non-null id of the ordinance type to be deleted and returns the deleted OrdinanceType object, which contains information about the ordinance type.
    deleteOrdinanceType(
      id: ID!
    ): OrdinanceType
  4. AccessToken GraphQL object reference

    The AccessToken object represents information about an access token in the Kavitro GraphQL API. It is returned by the accessToken query and the createAccessToken, revokeAccessToken, and updateAccessToken mutations. It is also a member of the AccessTokenEdge object.
    type AccessToken {
      id: ID!
      title: String
      permissions: [AccessTokenScope]
      allowedIps: [String!]
      token: String
      createdAt: DateTimeTz!
      updatedAt: DateTimeTz!
      deletedAt: DateTimeTz
      scopes(
        first: Int!
        after: String
      ): RoleConnection!
    }
  5. Create a new numbering series using the createNumberingSeries mutation

    The createNumberingSeries mutation allows you to create a new numbering series. It requires a non-null CreateNumberingSeriesInput object and returns a non-null NumberingSeries object containing the information about the newly created series.
    createNumberingSeries(
      input: CreateNumberingSeriesInput!
    ): NumberingSeries!
  6. Notification GraphQL Object Reference

    The Notification object represents information about a notification in the system. It is returned by the markNotificationAsRead and markNotificationAsUnread mutations and is a member of the NotificationEdge object.
    type Notification {
      id: String!
      type: NotificationType!
      causer: User
      data: NotificationData
      createdAt: DateTimeTz!
      updatedAt: DateTimeTz!
      seenAt: DateTimeTz
      readAt: DateTimeTz
    }
  7. Delete a numbering series using deleteNumberingSeries mutation

    The deleteNumberingSeries mutation allows for the deletion of a specific numbering series. It requires a non-null id of type ID! and returns a NumberingSeries object containing information about the deleted series.
    deleteNumberingSeries(
      id: ID!
    ): NumberingSeries
  8. Create a new specification using the createSpecification mutation

    The createSpecification mutation is used to create a new specification. It requires a non-null CreateSpecificationInput object and returns a non-null Specification object containing the information about the created specification.
    createSpecification(
      input: CreateSpecificationInput!
    ): Specification!