A postgres gateway **user** (also a typical postgres user) owns the foreign tables (built in or custom). The created postgres user only has access to use foreign tables and cannot directly create tables users. To create foreign tables use the Postgres Gateway Tables APIs
openapi: 3.1.0
info:
title: Cognite 3D Asset Mapping Postgres Gateway Users API
description: "# Introduction\nThis is the reference documentation for the Cognite API with\nan overview of all the available methods.\n\n# Postman\nSelect the **Download** button to download our OpenAPI specification to get started.\n\nTo import your data into Postman, select **Import**, and the Import modal opens.\nYou can import items by dragging or dropping files or folders. You can choose how to import your API and manage the import settings in **View Import Settings**.\n\nIn the Import Settings, set the **Folder organization** to **Tags**, select\n**Enable optional parameters** to turn off the settings, and select **Always inherit authentication** to turn on the settings. Select **Import**.\n\nSet the Authorization to **Oauth2.0**. By default, the settings are for Open Industrial Data. Navigate to [Cognite Hub](https://hub.cognite.com/open-industrial-data-211) to understand how to get the credentials for use in Postman.\n\nFor more information, see [Getting Started with Postman](https://developer.cognite.com/dev/guides/postman/).\n\n# Pagination\nMost resource types can be paginated, indicated by the field `nextCursor` in the response.\nBy passing the value of `nextCursor` as the cursor you will get the next page of `limit` results.\nNote that all parameters except `cursor` has to stay the same.\n\n# Parallel retrieval\nAs general guidance, Parallel Retrieval is a technique that should be used when due to query complexity, retrieval of data in a single request is significantly slower than it would otherwise be for a simple request. Parallel retrieval does not act as a speed multiplier on optimally running queries. By parallelizing such requests, data retrieval performance can be tuned to meet the client application needs. \n\nCDF supports parallel retrieval through the `partition` parameter, which has the format `m/n` where `n` is the amount of partitions you would like to split the entire data set into.\nIf you want to download the entire data set by splitting it into 10 partitions, do the following in parallel with `m` running from 1 to 10:\n - Make a request to `/events` with `partition=m/10`.\n - Paginate through the response by following the cursor as explained above. Note that the `partition` parameter needs to be passed to all subqueries.\n\nProcessing of parallel retrieval requests is subject to concurrency quota availability. The request returns the `429` response upon exceeding concurrency limits. See the Request throttling chapter below.\n\nTo prevent unexpected problems and to maximize read throughput, you should at most use 10 partitions. \nSome CDF resources will automatically enforce a maximum of 10 partitions.\nFor more specific and detailed information, please read the ```partition``` attribute documentation for the CDF resource you're using. \n\n# Requests throttling\nCognite Data Fusion (CDF) returns the HTTP `429` (too many requests) response status code when project capacity exceeds the limit.\n\nThe throttling can happen:\n - If a user or a project sends too many (more than allocated) concurrent requests.\n - If a user or a project sends a too high (more than allocated) rate of requests in a given amount of time.\n\nCognite recommends using a retry strategy based on truncated exponential backoff to handle sessions with HTTP response codes 429.\n\nCognite recommends using a reasonable number (up to 10) of `Parallel retrieval` partitions.\n\nFollowing these strategies lets you slow down the request frequency to maximize productivity without having to re-submit/retry failing requests.\n\nSee more [here](https://docs.cognite.com/dev/concepts/resource_throttling).\n\n# API versions\n## Version headers\nThis API uses calendar versioning, and version names follow the `YYYYMMDD` format.\nYou can find the versions currently available by using the version selector at the top of this page.\n\nTo use a specific API version, you can pass the `cdf-version: $version` header along with your requests to the API.\n\n## Beta versions\nThe beta versions provide a preview of what the stable version will look like in the future.\nBeta versions contain functionality that is reasonably mature, and highly likely to become a part of the stable API.\n\nBeta versions are indicated by a `-beta` suffix after the version name. For example, the beta version header for the\n2023-01-01 version is then `cdf-version: 20230101-beta`.\n\n## Alpha versions\nAlpha versions contain functionality that is new and experimental, and not guaranteed to ever become a part of the stable API.\nThis functionality presents no guarantee of service, so its use is subject to caution.\n\nAlpha versions are indicated by an `-alpha` suffix after the version name. For example, the alpha version header for\nthe 2023-01-01 version is then `cdf-version: 20230101-alpha`."
version: v1
contact:
name: Cognite Support
url: https://support.cognite.com
email: support@cognite.com
servers:
- url: https://{cluster}.cognitedata.com/api/v1/projects/{project}
description: The URL for the CDF cluster to connect to
variables:
cluster:
enum:
- api
- az-tyo-gp-001
- az-eastus-1
- az-power-no-northeurope
- westeurope-1
- asia-northeast1-1
- gc-dsm-gp-001
default: api
description: The CDF cluster to connect to
project:
default: publicdata
description: The CDF project name.
security:
- oidc-token:
- https://{cluster}.cognitedata.com/.default
- oauth2-client-credentials:
- https://{cluster}.cognitedata.com/.default
- oauth2-open-industrial-data:
- https://api.cognitedata.com/.default
- oauth2-auth-code:
- https://{cluster}.cognitedata.com/.default
tags:
- name: Postgres Gateway Users
description: 'A postgres gateway **user** (also a typical postgres user) owns the foreign tables (built in or custom).
The created postgres user only has access to use foreign tables and cannot directly create tables users. To create foreign tables use the Postgres Gateway Tables APIs
'
paths:
/postgresgateway:
get:
tags:
- Postgres Gateway Users
operationId: list_users
x-capability:
- postgresGateway:READ
parameters:
- $ref: '#/components/parameters/100Limit_'
- $ref: '#/components/parameters/Cursor'
description: '
> **Required capabilities:** `postgresGateway:READ`
List all users in a given project. If more than `limit` users exist, a cursor for pagination will be returned with the response.'
responses:
'200':
description: List of users paginated
content:
application/json:
schema:
$ref: '#/components/schemas/ItemsWithCursor_User_'
'400':
$ref: '#/components/responses/400ErrorResponse'
'422':
$ref: '#/components/responses/ValidationError_'
summary: List users
post:
tags:
- Postgres Gateway Users
operationId: create_users
x-capability:
- postgresGateway:WRITE
description: '
> **Required capabilities:** `postgresGateway:WRITE`
Create postgres users.'
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/Items_CreateUser_'
description: List of postgres users to create
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/ItemsWithCursor_UserCreated_'
description: List of created users
'400':
description: Response of a failed request
$ref: '#/components/responses/400ErrorResponse'
'422':
$ref: '#/components/responses/ValidationError_'
summary: Create users
x-code-samples:
- lang: Python
label: Python SDK
source: "import os\nfrom cognite.client.data_classes.postgres_gateway import UserWrite, SessionCredentials\nfrom cognite.client.data_classes import ClientCredentials\nsession = client.iam.sessions.create(\n ClientCredentials(os.environ[\"IDP_CLIENT_ID\"], os.environ[\"IDP_CLIENT_SECRET\"]),\n session_type=\"CLIENT_CREDENTIALS\"\n)\nuser = UserWrite(credentials=SessionCredentials(nonce=session.nonce))\nres = client.postgres_gateway.users.create(user)\n"
/postgresgateway/list:
post:
summary: Filter users
tags:
- Postgres Gateway Users
operationId: filter_users
description: List all postgres users for a given project. If more than `limit` users exist, a cursor for pagination will be returned with the response.
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/FilterUsers'
responses:
'200':
description: List of users paginated
content:
application/json:
schema:
$ref: '#/components/schemas/ItemsWithCursor_User_'
'400':
$ref: '#/components/responses/400ErrorResponse'
'422':
$ref: '#/components/responses/ErrorResponse'
description: Validation Error
x-code-samples:
- lang: Python
label: Python SDK
source: "user_list = client.postgres_gateway.users.list(limit=5)\n\nfor user in client.postgres_gateway.users:\n user # do something with the user\n\nfor user_list in client.postgres_gateway.users(chunk_size=25):\n user_list # do something with the users\n"
/postgresgateway/byids:
post:
tags:
- Postgres Gateway Users
operationId: retreive_users
x-capability: postgresGateway:READ
description: '
> **Required capabilities:** `postgresGateway:READ`
Retreive a list of postgres users by their usernames, optionally ignoring unknown usernames'
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/ItemsWithIgnoreUnknown_Username_'
responses:
'200':
description: List of users retrieved by their usernames
content:
application/json:
schema:
$ref: '#/components/schemas/ItemsWithoutCursor_User_'
'400':
$ref: '#/components/responses/400ErrorResponse'
description: Response of a failed request
'422':
$ref: '#/components/responses/ValidationError_'
summary: Retrieve users
x-code-samples:
- lang: Python
label: Python SDK
source: 'res = client.postgres_gateway.users.retrieve("myUser", ignore_unknown_ids=True)
'
/postgresgateway/update:
post:
tags:
- Postgres Gateway Users
operationId: update_users
x-capability:
- postgresGateway: postgresGateway:WRITE
description: '
> **Required capabilities:** `[object Object]`
Update postgres users'
requestBody:
required: true
description: Users to update
content:
application/json:
schema:
$ref: '#/components/schemas/Items_UserUpdate_'
responses:
'200':
description: Returns users with updates
content:
application/json:
schema:
$ref: '#/components/schemas/ItemsWithCursor_User_'
'400':
$ref: '#/components/responses/400ErrorResponse'
'422':
$ref: '#/components/responses/ValidationError_'
summary: Update users
x-code-samples:
- lang: Python
label: Python SDK
source: "import os\nfrom cognite.client.data_classes.postgres_gateway import UserUpdate, SessionCredentials\nfrom cognite.client.data_classes import ClientCredentials\nsession = client.iam.sessions.create(\n ClientCredentials(os.environ[\"IDP_CLIENT_ID\"], os.environ[\"IDP_CLIENT_SECRET\"]),\n session_type=\"CLIENT_CREDENTIALS\"\n)\nupdate = UserUpdate('myUser').credentials.set(SessionCredentials(nonce=session.nonce))\nres = client.postgres_gateway.users.update(update)\n"
/postgresgateway/delete:
post:
tags:
- Postgres Gateway Users
operationId: delete_users
x-capability:
- postgresGateway: WRITE
description: '
> **Required capabilities:** `[object Object]`
Delete postgres users'
requestBody:
required: true
description: Postgres users to delete
content:
application/json:
schema:
$ref: '#/components/schemas/ItemsWithIgnoreUnknown_Username_1_'
responses:
'200':
$ref: '#/components/responses/EmptyResponse'
'400':
$ref: '#/components/responses/400ErrorResponse'
'422':
$ref: '#/components/responses/ValidationError_'
summary: Delete users
x-code-samples:
- lang: Python
label: Python SDK
source: 'client.postgres_gateway.users.delete(["myUser", "myUser2"])
'
components:
schemas:
UpdateItem_SessionCredentials:
additionalProperties: false
properties:
set:
$ref: '#/components/schemas/SessionCredentials'
required:
- set
title: UpdateItem_SessionCredentials
type: object
description: Set a new set of session credentials for writing to CDF.
UsernameWrapper:
type: object
additionalProperties: false
required:
- username
properties:
username:
$ref: '#/components/schemas/Username'
ValidationErrorContent_:
type: object
required:
- code
- message
description: Cognite API error.
properties:
code:
type: integer
description: HTTP status code.
format: int32
example: 422
message:
type: string
description: Error message.
example: 'Extra inputs are not permitted: type'
Error:
type: object
required:
- code
- message
description: Cognite API error.
properties:
code:
type: integer
description: HTTP status code.
format: int32
example: 401
message:
type: string
description: Error message.
example: Could not authenticate.
missing:
type: array
description: List of lookup objects that do not match any results.
items:
type: object
additionalProperties: true
duplicated:
type: array
description: List of objects that are not unique.
items:
type: object
additionalProperties: true
UpdateUser:
additionalProperties: false
type: object
properties:
credentials:
$ref: '#/components/schemas/UpdateItem_SessionCredentials'
Username:
type: string
title: Username
description: Username to authenticate the user on the DB.
FilterUsers:
type: object
additionalProperties: false
title: Filter Users
properties:
limit:
type: integer
minimum: 1
maximum: 10
format: int32
cursor:
type: string
title: Cursor
description: Cursor for pagination
UserUpdateItem:
type: object
additionalProperties: false
required:
- username
- update
properties:
username:
$ref: '#/components/schemas/Username'
update:
$ref: '#/components/schemas/UpdateUser'
ItemsWithoutCursor_User_:
type: object
additionalProperties: false
properties:
items:
items:
$ref: '#/components/schemas/FdwUser'
title: Items
type: array
minItems: 0
required:
- items
ItemsWithIgnoreUnknown_Username_:
type: object
additionalProperties: false
required:
- items
properties:
items:
items:
$ref: '#/components/schemas/UsernameWrapper'
type: array
maxItems: 10
minItems: 1
ignoreUnknownIds:
type: boolean
description: Ignore usernames that are not found
EpochTimestamp:
description: The number of milliseconds since 00:00:00 Thursday, 1 January 1970, Coordinated Universal Time (UTC), minus leap seconds.
type: integer
minimum: 0
format: int64
example: 1730204346000
Items_UserUpdate_:
additionalProperties: false
title: Items[UserUpdate]
type: object
required:
- items
properties:
items:
items:
$ref: '#/components/schemas/UserUpdateItem'
title: Items
maxItems: 1
minItems: 1
Items_CreateUser_:
type: object
additionalProperties: false
title: CreateUser list
required:
- items
properties:
items:
items:
$ref: '#/components/schemas/CreateUser'
title: Items
type: array
minItems: 1
maxItems: 1
ItemsWithCursor_User_:
type: object
additionalProperties: false
properties:
items:
items:
$ref: '#/components/schemas/FdwUser'
title: Items
type: array
maxItems: 100
minItems: 0
nextCursor:
type: string
title: Next cursor
description: Cursor for pagination
required:
- items
CreateUser:
type: object
title: Create User
additionalProperties: false
required:
- credentials
properties:
credentials:
$ref: '#/components/schemas/SessionCredentials'
ItemsWithIgnoreUnknown_Username_1_:
type: object
additionalProperties: false
required:
- items
properties:
items:
items:
$ref: '#/components/schemas/UsernameWrapper'
type: array
maxItems: 1
minItems: 1
ignoreUnknownIds:
type: boolean
description: Ignore usernames that are not found
ItemsWithCursor_UserCreated_:
type: object
additionalProperties: false
properties:
items:
items:
$ref: '#/components/schemas/UserCreated'
title: Items
type: array
minItems: 1
maxItems: 1
required:
- items
UserCreated:
type: object
required:
- username
- password
- createdTime
- host
description: A user
properties:
host:
type: string
title: Host
description: The connection host for the postgres instance.
example: fdw.<CLUSTER>.cogniteapp.com
username:
$ref: '#/components/schemas/Username'
password:
type: string
title: Password
description: Password to authenticate the user on the DB.
createdTime:
$ref: '#/components/schemas/EpochTimestamp'
lastUpdatedTime:
$ref: '#/components/schemas/EpochTimestamp'
sessionId:
type: integer
title: Session ID
minimum: 1
maximum: 9007199254740991
format: int64
description: ID of the session tied to this user.
FdwUser:
type: object
required:
- username
- createdTime
description: A user
properties:
username:
$ref: '#/components/schemas/Username'
createdTime:
$ref: '#/components/schemas/EpochTimestamp'
lastUpdatedTime:
$ref: '#/components/schemas/EpochTimestamp'
sessionId:
type: integer
title: Session ID
minimum: 1
maximum: 9007199254740991
format: int64
description: ID of the session tied to this user.
SessionCredentials:
additionalProperties: false
properties:
nonce:
title: Nonce
type: string
description: Session nonce for a recently created CDF Session.
required:
- nonce
title: SessionCredentials
type: object
description: Credentials for authenticating towards CDF using a CDF session.
responses:
ValidationError_:
description: Validation Error
content:
application/json:
schema:
type: object
required:
- error
properties:
error:
$ref: '#/components/schemas/ValidationErrorContent_'
ErrorResponse:
description: The response for a failed request.
content:
application/json:
schema:
type: object
required:
- error
properties:
error:
$ref: '#/components/schemas/Error'
400ErrorResponse:
description: The response for a bad request.
content:
application/json:
schema:
type: object
required:
- error
properties:
error:
$ref: '#/components/schemas/Error'
example:
error:
code: 400
message: '`null` values aren''t allowed.'
EmptyResponse:
description: Empty response.
content:
application/json:
schema:
type: object
parameters:
Cursor:
name: cursor
description: 'Cursor for paging through results. In general, if a response contains a `nextCursor`
property, it means that there may be more results, and you should pass that value as the
`cursor` parameter in the next request.
Note that the cursor may or may not be encrypted, but either way, it is not intended to be
decoded. Its internal structure is not a part of the public API, and may change without
notice. You should treat it as an opaque string and not attempt to craft your own cursors.
'
in: query
schema:
type: string
example: 4zj0Vy2fo0NtNMb229mI9r1V3YG5NBL752kQz1cKtwo
100Limit_:
name: limit
description: Limits the number of results to be returned. The maximum results returned by the server is 100 even if you specify a higher limit.
in: query
schema:
type: integer
default: 100
minimum: 1
maximum: 100
securitySchemes:
oidc-token:
type: http
scheme: bearer
bearerFormat: OpenID Connect or OAuth2 token
description: Access token issued by the CDF project's configured identity provider. Access token must be an OpenID Connect token, and the project must be configured to accept OpenID Connect tokens. Use a header key of 'Authorization' with a value of 'Bearer $accesstoken'. The token can be obtained through any flow supported by the identity provider.
oauth2-client-credentials:
type: oauth2
description: Access token issued by the CDF project's configured identity provider. Access token must be an OpenID Connect token, and the project must be configured to accept OpenID Connect tokens. Use a header key of 'Authorization' with a value of 'Bearer $accesstoken'. The token can be obtained through any flow supported by the identity provider.
flows:
clientCredentials:
tokenUrl: https://your-idps.token.url/
scopes:
default: https://{cluster}.cognitedata.com/.default
oauth2-auth-code:
type: oauth2
description: Access token issued by the CDF project's configured identity provider. Access token must be an OpenID Connect token, and the project must be configured to accept OpenID Connect tokens. Use a header key of 'Authorization' with a value of 'Bearer $accesstoken'. The token can be obtained through any flow supported by the identity provider.
flows:
authorizationCode:
authorizationUrl: https://your-idps.authorization.url/
tokenUrl: https://your-idps.token.url/
scopes:
default: https://{cluster}.cognitedata.com/.default
oauth2-open-industrial-data:
type: oauth2
description: Auth flow for Open Industrial Data. Get your client secret from https://hub.cognite.com/open-industrial-data-211.
flows:
clientCredentials:
tokenUrl: https://login.microsoftonline.com/48d5043c-cf70-4c49-881c-c638f5796997/oauth2/v2.0/token
scopes:
default: https://api.cognitedata.com/.default
org-oidc-token:
type: openIdConnect
openIdConnectUrl: https://auth.cognite.com/.well-known/openid-configuration
description: 'Access token issued by the Cognite authorization server, and valid for the target organization. The token must
be an OpenID Connect token, and it can be obtained by performing an OIDC login flow toward `auth.cognite.com`.
This is a single URL for all CDF organizations.'
x-tagGroups:
- name: Changelog
tags:
- Changelog
- name: Organizations and projects
tags:
- Organizations
- Projects
- name: Identity and access management
tags:
- Principals
- Groups
- Security categories
- Sessions
- Token
- User profiles
- Project Deletion Reporting
- name: Data modeling
tags:
- Data Modeling
- Data models
- Spaces
- Views
- Containers
- Nodes
- Instances
- Statistics
- Streams
- Records
- name: Asset-centric data model
tags:
- Assets
- Time series
- Synthetic Time Series
- Data point subscriptions
- Events
- Files
- Sequences
- Geospatial
- Seismic
- name: 3D
tags:
- 3D Models
- 3D Model Revisions
- 3D Files
- 3D Asset Mapping
- 3D Contextualization
- 3D Jobs
- 3D Migration
- 3D Scenes
- name: Contextualization
tags:
- Entity matching
- Entity matching pipelines
- Engineering diagrams
- Vision
- Advanced joins
- name: Cognite AI
tags:
- Agents
- Skills
- Chat Completions
- Document AI
- Models
- name: Documents
tags:
- Documents
- Document preview
- name: Data ingestion
tags:
- Raw
- Extraction Pipelines
- Extraction Pipelines Runs
- Extraction Pipelines Config
- Extractors
- name: Data organization
tags:
- Data sets
- Data domains
- Data products
- Rule sets
- Labels
- Relationships
- Annotations
- name: Transformations
tags:
- Transformations
- Transformation Jobs
- Transformation Schedules
- Transformation Notifications
- Query
- Schema
- name: Functions
tags:
- Functions
- Function calls
- Function schedules
- name: Hosted Extractors
tags:
- Sources
- Jobs
- Destinations
- Mappings
- name: PostgreSQL Gateway
tags:
- Postgres Gateway Users
- Postgres Gateway Tables
- name: SAP Writeback
tags:
- SAP Instances
- SAP Endpoints
- Schema Mappings
- Writeback Requests
- name: Data workflows
tags:
- Workflows
- Workflow versions
- Workflow executions
- Workflow triggers
- Tasks
- Workers
- name: Simulators
tags:
- Simulators
- Simulator Integrations
- Simulator Models
- Simulator Routines
- Simulation Runs
- Simulator Logs
- name: Units
tags:
- Units
- Unit Systems
- name: ''
tags:
- ''