Skip to main content

API Wrapper for the Stimline IDEX collaboration platform software used for well intervention.

Project description

Stimline IDEX Software API Wrapper for Python

Ruff

The stimline-idex package is an abstraction layer developed for interacting with the Stimline IDEX Collaboration software API.

It is based on available API documentation for the Aker BP IDEX environment publicly available here.

The Wrapper currently supports API version 1.0.

Getting started

To install:

pip install stimline-idex

Usage is fairly simple. You can authenticate using an X-API-KEY or using a JWT auth flow that requests a bearer token from the authentication endpoint.

from stimline_idex.v1 import ApiKeyAuth, IDEXClient, JwtAuth
from stimline_idex.v1 import data_schemas as IDEXSchemas

api_auth = ApiKeyAuth(
    base_url = "https://<env>.idexcloud.net/idexapi/1.0/",
    x_api_key = "00000000-0000-0000-0000-000000000000"
)

client = IDEXClient(api_auth)

jwt_auth = JWTAuth(
    base_url = "https://<env>.idexcloud.net/idexapi/1.0/",
    username = "foo",
    password = "bar"
)

client_jwt = IDEXClient(jwt_auth)

The different modules are available for interaction, to get top 3 recently created wellbores:

wellbores = client.wellbores.get(top=3, order_by="createdDate desc")

Some API endpoints return soft deleted records. The wrapper excludes deleted records in the query to the API (or filters the response prior to returning data), by default. This is because retrieving deleted data may lead to confusing results (e.g. several wellbores with the same name).

You can override this by using a keyword argument: include_soft_delete=True. This is only available for API endpoints that return objects that have a deletedDate attribute.

wellbores = client.wellbores.get(include_soft_delete=True)

To make it easier to use the different objects returned by the API, the wrapper uses Pydantic to validate that the return payload is according to the API specifications, the types are correctly parsed (e.g. as datetime objects instead of strings) and also provides a dot notation interface for working with object attributes:

wellbores = client.wellbores.get(top=3)

for wellbore in wellbores:
    print(wellbore.name)

Some of the endpoints allow for OData filtering. The filter string is passed directly to the API, it is up to the end user to ensure that this is in a correct format. The column names used in the filtering expression must be according to the API specification (i.e. not snake_cased). See the official Odata documentation for filtering inspiration..

Note: Filtering on the deletedDate attribute and not having include_soft_delete=True will emit a warning log.

from datetime import datetime, timezone

cutoff_date = datetime(2024, 1, 1, tzinfo=timezone.utc)

wellbores = client.wellbores.get(filter=f"createdDate gt {cutoff_date.isoformat()}")

You can also select a subset of columns instead of having the API return all columns. This can be useful for reducing the response time for use-cases where the full response is not required.

Note: Currently the API modifies the response JSON when a $select clause is passed.

The current behavior (from 0.3.0) is to disregard the select clause when sending a request to the API, to avoid validation errors. Warning logs are emitted to reflect this.

from datetime import datetime, timezone

cutoff_date = datetime(2024, 1, 1, tzinfo=timezone.utc)
filter_str = f"createdDate gt {cutoff_date.isoformat()}"
colummns = ["name","modifiedDate"]

client.wellbores.get(filter=filter_str, select=columns)

For endpoints that require hierarchical context (e.g. retrieving all wellbores for a given well), you can pass either the parent object returned by the wrapper, or the appropriate id as a string. It is left as an exercise to the user to create further functions to loop over an iterable to retrieve children for multiple parents if that is required.

# By arbitrary `Well` object from API
well = client.wells.get(top=1)[0]
wellbores = client.wellbores.get(well=well)
# By specific `Well` by id
well_id = "abc"
wellbores = client.wellbores.get(well_id=well_id)

For endpoints that support retrieval of a given object by id, pass this as a string:

wellbore_id = "abc"
wellbore = client.wellbores.get(id=wellbore_id)

Logs

This package emits logs on the stimline-idex logger.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

stimline_idex-0.4.1.tar.gz (21.7 kB view details)

Uploaded Source

Built Distribution

stimline_idex-0.4.1-py3-none-any.whl (37.0 kB view details)

Uploaded Python 3

File details

Details for the file stimline_idex-0.4.1.tar.gz.

File metadata

  • Download URL: stimline_idex-0.4.1.tar.gz
  • Upload date:
  • Size: 21.7 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: poetry/1.7.1 CPython/3.11.6 Windows/10

File hashes

Hashes for stimline_idex-0.4.1.tar.gz
Algorithm Hash digest
SHA256 25f46aeb4ca6f1bb20262f49428dadea12f6180634a5f40abe4cc9bf2de197d1
MD5 7e6fdfb7737571f6865fff53212fff55
BLAKE2b-256 b9b27648668ddfe3df970f374fb5eae9b571a974fe33c37a7099ebb1598771d0

See more details on using hashes here.

File details

Details for the file stimline_idex-0.4.1-py3-none-any.whl.

File metadata

  • Download URL: stimline_idex-0.4.1-py3-none-any.whl
  • Upload date:
  • Size: 37.0 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: poetry/1.7.1 CPython/3.11.6 Windows/10

File hashes

Hashes for stimline_idex-0.4.1-py3-none-any.whl
Algorithm Hash digest
SHA256 fadd2e41e16991eb27fba367e90a710c84f86b948511277bbb66743d5a2c0c52
MD5 868695d66ccfa89393f789001caf0eb8
BLAKE2b-256 47a2d207c66181504e50a0d5ff3cd4f1d71af1c6968741899879ac97c9dafd57

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page