PostV3WellsResponse

Maritime IntelligenceEnergy IntelligenceSatellite DataAI AnalyticsVessel TrackingOil & Gas Monitoring

Properties

Name	Type	Description
api	integer	An API is a unique, permanent, numeric identifier assigned to each well drilled.
completion_date	string	Date on which the well was completed. Date formatting - [“YYYY-MM-DD”].
county	string	County in the state where the well is located.
horizontal_length	integer	The horizontal length of a well in feet.
lat	string	The latitude of the location, in decimal degrees; follows the WGS 84/EPSG:4326 coordinate system.
lat_bottomhole	number	Latitude of the well’s bottomhole location.
lon_bottomhole	number	Longitude of the well’s bottomhole location.
long	string	The longitude of the location, in decimal degrees; follows the WGS 84/EPSG:4326 coordinate system.
measured_depth	integer	The measured operating depth of a well in feet.
operator_name	string	Operator of the well.
permit_date	string	The date on which the well permit was authorized. Date formatting - [“YYYY-MM-DD”].
production_first_date	string	( Unsynced ) date on which the well was first productive after completion. Date formatting - [“YYYY-MM-DD”].
region	string	Aggregation of multiple major producing basins.
spud_date	string	Spudding is the day the main drill bit enters the ground. Date formatting - [“YYYY-MM-DD”].
state_ab	string	Abbreviation of the state.
sub_region	string	Aggregation of several counties, typically representing a major producing basin.
total_vertical_depth	integer	The total vertical depth of an operating well in feet.
wellbore_type	string	The orientation of the well bore used to locate and extract oil and gas from a well. Valid types are ‘vertical’, ‘horizontal’, and ‘directional’.
wellpad_id	string	Identifier of the wellpad.

View JSON Schema on GitHub

JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://artifacts.apis.io/synmax/json-schema/synmax-post-v3-wells-response-schema.json",
  "title": "PostV3WellsResponse",
  "x-generated": "2026-11-09",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/_ae-authored/synmax-openapi-generated.yml#/components/schemas/PostV3WellsResponse",
  "type": "object",
  "properties": {
    "api": {
      "type": "integer",
      "description": "An API is a unique, permanent, numeric identifier assigned to each well drilled."
    },
    "completion_date": {
      "type": "string",
      "description": "Date on which the well was completed. Date formatting - [“YYYY-MM-DD”]."
    },
    "county": {
      "type": "string",
      "description": "County in the state where the well is located."
    },
    "horizontal_length": {
      "type": "integer",
      "description": "The horizontal length of a well in feet."
    },
    "lat": {
      "type": "string",
      "description": "The latitude of the location, in decimal degrees; follows the WGS 84/EPSG:4326 coordinate system."
    },
    "lat_bottomhole": {
      "type": "number",
      "description": "Latitude of the well’s bottomhole location."
    },
    "lon_bottomhole": {
      "type": "number",
      "description": "Longitude of the well’s bottomhole location."
    },
    "long": {
      "type": "string",
      "description": "The longitude of the location, in decimal degrees; follows the WGS 84/EPSG:4326 coordinate system."
    },
    "measured_depth": {
      "type": "integer",
      "description": "The measured operating depth of a well in feet."
    },
    "operator_name": {
      "type": "string",
      "description": "Operator of the well."
    },
    "permit_date": {
      "type": "string",
      "description": "The date on which the well permit was authorized. Date formatting - [“YYYY-MM-DD”]."
    },
    "production_first_date": {
      "type": "string",
      "description": "( Unsynced ) date on which the well was first productive after completion. Date formatting - [“YYYY-MM-DD”]."
    },
    "region": {
      "type": "string",
      "description": "Aggregation of multiple major producing basins."
    },
    "spud_date": {
      "type": "string",
      "description": "Spudding is the day the main drill bit enters the ground. Date formatting - [“YYYY-MM-DD”]."
    },
    "state_ab": {
      "type": "string",
      "description": "Abbreviation of the state."
    },
    "sub_region": {
      "type": "string",
      "description": "Aggregation of several counties, typically representing a major producing basin."
    },
    "total_vertical_depth": {
      "type": "integer",
      "description": "The total vertical depth of an operating well in feet."
    },
    "wellbore_type": {
      "type": "string",
      "description": "The orientation of the well bore used to locate and extract oil and gas from a well. Valid types are ‘vertical’, ‘horizontal’, and ‘directional’."
    },
    "wellpad_id": {
      "type": "string",
      "description": "Identifier of the wellpad."
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this

find_json_schemasBrowse and filter every JSON Schema in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This JSON Schema

curl "https://apis.io/api/v1/json-schemas/synmax-post-v3-wells-response"

All schemas

curl "https://apis.io/api/v1/json-schemas?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.