search_wellbores

Search wellbores drilled on the Norwegian continental shelf.

Direct GET

For navigating agents: open the HTML page with parameters in the URL. The result is fetched and displayed without screenshots or form filling.

https://allemannsdata.com/wiki/kilder/sodir/search_wellbores/?name={name}&field={field}&operator={operator}&production_licence={production_licence}&purpose={purpose}&status={status}&content={content}&kind=all&from_year={from_year}&to_year={to_year}&limit=50&offset=0

Replace {name}, {field}, {operator}, {production_licence}, {purpose}, {status}, {content}, {kind}, {from_year}, {to_year}, {limit} with values. Remove unused optional parameters from the URL.

For software and dashboards: Read the operation descriptor. The JSON GET template is https://allemannsdata.com/wiki/api/v1/kilder/sodir/search_wellbores?name={name}&field={field}&operator={operator}&production_licence={production_licence}&purpose={purpose}&status={status}&content={content}&kind=all&from_year={from_year}&to_year={to_year}&limit=50&offset=0.

ParameterRequirementJSON typeDescription
nameoptionalunionPartial wellbore name, e.g. "16/2-6" (the Johan Sverdrup discovery well) or "34/10".
fieldoptionalunionPartial field name the wellbore belongs to, e.g. "OSEBERG".
operatoroptionalunionPartial drilling operator name, e.g. "Equinor".
production_licenceoptionalunionLicence number the wellbore was drilled under, e.g. "265".
purposeoptionalunion"WILDCAT", "APPRAISAL", "PRODUCTION", "INJECTION", "WILDCAT-CCS", "APPRAISAL-CCS" or similar.
statusoptionalunione.g. "PRODUCING", "P&A" (plugged and abandoned), "INJECTING", "ONLINE/OPERATIONAL", "SUSPENDED".
contentoptionalunionWhat the wellbore encountered or carries: "OIL", "GAS", "OIL/GAS", "DRY", "WATER", "CO2".
kindoptionalstringWhich register to search: "exploration", "development", "other" (shallow/soil drilling and the like) or "all" (default).
from_yearoptionalunionInclusive bounds on the entry (spud) year.
to_yearoptionalunionInclusive bounds on the entry (spud) year.
limitoptionalintegerMaximum wellbores to return (default 50, max 200).
offsetoptionalintegerNumber of list items to skip; default 0.
Generated JavaScript, Python and response structure

Use JSON when the user requests code, machine-readable data, value extraction or further computation. Use the HTML GET page to identify the correct source and verify parameters.

Example for generated JavaScript and Python

https://allemannsdata.com/wiki/api/v1/kilder/sodir/search_wellbores?name={name}&field={field}&operator={operator}&production_licence={production_licence}&purpose={purpose}&status={status}&content={content}&kind=all&from_year={from_year}&to_year={to_year}&limit=50&offset=0

Replace URL placeholders and remove unused optional parameters.

JavaScript in a dashboard

const url = "https://allemannsdata.com/wiki/api/v1/kilder/sodir/search_wellbores?name={name}&field={field}&operator={operator}&production_licence={production_licence}&purpose={purpose}&status={status}&content={content}&kind=all&from_year={from_year}&to_year={to_year}&limit=50&offset=0";
const response = await fetch(url);
if (!response.ok) {
  const failure = await response.json();
  throw new Error(`${failure.error.code}: ${failure.error.message} ${failure.suggestion}`);
}
const result = await response.json();
const data = result.data;

Python without additional packages

import json
from urllib.request import urlopen

url = "https://allemannsdata.com/wiki/api/v1/kilder/sodir/search_wellbores?name={name}&field={field}&operator={operator}&production_licence={production_licence}&purpose={purpose}&status={status}&content={content}&kind=all&from_year={from_year}&to_year={to_year}&limit=50&offset=0"
with urlopen(url) as response:
    result = json.load(response)
data = result["data"]

Response structure

{
  "source": "sodir",
  "operation": "search_wellbores",
  "parameters": {},
  "data": {},
  "entities": [],
  "_meta": {"retrieved_at": "...", "sources": [], "cache": {}},
  "_links": {"self": "...", "source": "...", "wiki": "...", "feedback": "..."}
}
Form for manual use

The form is a fallback for people and browser agents that cannot open the GET URL directly.

Type: string. Partial wellbore name, e.g. "16/2-6" (the Johan Sverdrup discovery well) or "34/10".
Type: string. Partial field name the wellbore belongs to, e.g. "OSEBERG".
Type: string. Partial drilling operator name, e.g. "Equinor".
Type: string. Licence number the wellbore was drilled under, e.g. "265".
Type: string. "WILDCAT", "APPRAISAL", "PRODUCTION", "INJECTION", "WILDCAT-CCS", "APPRAISAL-CCS" or similar.
Type: string. e.g. "PRODUCING", "P&A" (plugged and abandoned), "INJECTING", "ONLINE/OPERATIONAL", "SUSPENDED".
Type: string. What the wellbore encountered or carries: "OIL", "GAS", "OIL/GAS", "DRY", "WATER", "CO2".
Type: string. Which register to search: "exploration", "development", "other" (shallow/soil drilling and the like) or "all" (default).
Type: integer. Inclusive bounds on the entry (spud) year.
Type: integer. Inclusive bounds on the entry (spud) year.
Type: integer. Maximum wellbores to return (default 50, max 200).

Continue exploring

How an AI agent should use this page

Ground rule: Navigate with HTML GET links to keep explanations and relationships. Use the page's JSON alternative only when concrete values must be extracted, compared or computed.

How to use the search_wellbores lookup

  1. Replace the placeholders in the HTML GET template; remove optional parameters you do not need.
  2. Check types, units, limits and ID formats in the parameter table.
  3. Follow linked results to canonical pages before combining sources.

Misreading to avoid: An empty list means "no results for this lookup". An error message or unavailable source does not mean the data does not exist.

Source-specific next step

Go to the source page for other operations. Use the JSON template only after the HTML result shows that the parameters and source are correct.