---
title: "add a new feature"
method: POST
path: "/items"
tags: ["Insert Extension"]
---

# add a new feature

`POST /items`

create a new feature

## Headers

- `Authorization` string, required
- `Prefer` string, required

## Request body

- union
  - Item — A GeoJSON Feature augmented with foreign members that contain values relevant to a STAC entity
    - `stac_version` string, required
    - `stac_extensions` union[]
      - union
        - string, uri
        - string
    - `id` string, required — Provider identifier, a unique ID, potentially a link to a file.
    - `bbox` number[], required — Only features that have a geometry that intersects the bounding box are selected. The bounding box is provided as four or six numbers, depending on whether the coordinate reference system includes a vertical axis (elevation or depth): * Lower left corner, coordinate axis 1 * Lower left corner, coordinate axis 2 * Lower left corner, coordinate axis 3 (optional) * Upper right corner, coordinate axis 1 * Upper right corner, coordinate axis 2 * Upper right corner, coordinate axis 3 (optional) The coordinate reference system of the values is WGS84 longitude/latitude (http://www.opengis.net/def/crs/OGC/1.3/CRS84) unless a different coordinate reference system is specified in the parameter `bbox-crs`. For WGS84 longitude/latitude the values are in most cases the sequence of minimum longitude, minimum latitude, maximum longitude and maximum latitude. However, in cases where the box spans the antimeridian the first value (west-most box edge) is larger than the third value (east-most box edge). If a feature has multiple spatial geometry properties, it is the decision of the server whether only a single spatial geometry property is used to determine the extent or all relevant geometries.
    - `geometry` GeometryJson, required — unresolved $ref
    - `type` 'Feature', required — The GeoJSON type
    - `properties` ItemProperties, required — provides the core metatdata fields plus extensions
      - `datetime` string, required — Either a date-time or an interval, open or closed. Date and time expressions adhere to RFC 3339. Open intervals are expressed using double-dots. Examples: * A date-time: "2019-04-12T23:20:50Z" * A closed interval: "2019-04-12T00:00:00Z/2019-08-18T21:31:12Z" Only features that have a temporal property that intersects the value of `datetime` are selected. If a feature has multiple temporal properties, it is the decision of the server whether only a single temporal property is used to determine the extent or all relevant temporal properties.
    - `links` Link[], required
      - `href` string, url, required
      - `rel` string, required
      - `type` string
      - `hreflang` string
      - `title` string
      - `length` integer
    - `assets` ItemAssets, required
  - ItemCollection — A GeoJSON FeatureCollection augmented with foreign members that contain values relevant to a STAC entity
    - `type` 'FeatureCollection', required
    - `features` Item[], required
      - `stac_version` string, required
      - `stac_extensions` union[]
        - union
          - string, uri
          - string
      - `id` string, required — Provider identifier, a unique ID, potentially a link to a file.
      - `bbox` number[], required — Only features that have a geometry that intersects the bounding box are selected. The bounding box is provided as four or six numbers, depending on whether the coordinate reference system includes a vertical axis (elevation or depth): * Lower left corner, coordinate axis 1 * Lower left corner, coordinate axis 2 * Lower left corner, coordinate axis 3 (optional) * Upper right corner, coordinate axis 1 * Upper right corner, coordinate axis 2 * Upper right corner, coordinate axis 3 (optional) The coordinate reference system of the values is WGS84 longitude/latitude (http://www.opengis.net/def/crs/OGC/1.3/CRS84) unless a different coordinate reference system is specified in the parameter `bbox-crs`. For WGS84 longitude/latitude the values are in most cases the sequence of minimum longitude, minimum latitude, maximum longitude and maximum latitude. However, in cases where the box spans the antimeridian the first value (west-most box edge) is larger than the third value (east-most box edge). If a feature has multiple spatial geometry properties, it is the decision of the server whether only a single spatial geometry property is used to determine the extent or all relevant geometries.
      - `geometry` GeometryJson, required — unresolved $ref
      - `type` 'Feature', required — The GeoJSON type
      - `properties` ItemProperties, required — provides the core metatdata fields plus extensions
        - `datetime` string, required — Either a date-time or an interval, open or closed. Date and time expressions adhere to RFC 3339. Open intervals are expressed using double-dots. Examples: * A date-time: "2019-04-12T23:20:50Z" * A closed interval: "2019-04-12T00:00:00Z/2019-08-18T21:31:12Z" Only features that have a temporal property that intersects the value of `datetime` are selected. If a feature has multiple temporal properties, it is the decision of the server whether only a single temporal property is used to determine the extent or all relevant temporal properties.
      - `links` Link[], required
        - `href` string, url, required
        - `rel` string, required
        - `type` string
        - `hreflang` string
        - `title` string
        - `length` integer
      - `assets` ItemAssets, required
    - `links` Link[] — An array of links. Can be used for pagination, e.g. by providing a link with the `next` relation type.
      - `href` string, url, required
      - `rel` string, required
      - `type` string
      - `hreflang` string
      - `title` string
      - `length` integer

## Response `201`

Status of the create request.

## Other responses

- `400` — The request was malformed or semantically invalid
- `409` — The request has a conflict
- `5XX` — The request was syntactically and semantically valid, but an error occurred while trying to act upon it
- `default` — An error occurred.

---

[API](https://skmtc.dev/developmentseed/apis/the-sat-api-pg-stac-api.md) · [All operations](https://skmtc.dev/developmentseed/apis/the-sat-api-pg-stac-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/developmentseed/the-sat-api-pg-stac-api/revisions/d77351000251/schema)
