m3ter 0.9.0

The official Python library for the m3ter API

M3ter Python API library

The M3ter Python library provides convenient access to the M3ter REST API from any Python 3.9+ application. The library includes type definitions for all request params and response fields, and offers both synchronous and asynchronous clients powered by httpx.

It is generated with Stainless.

MCP Server

Use the M3ter MCP Server to enable AI assistants to interact with this API, allowing them to explore endpoints, make test requests, and use documentation to help integrate this SDK into your application.

Note: You may need to set environment variables in your MCP client.

Documentation

The REST API documentation can be found on www.m3ter.com. The full API of this library can be found in api.md.

Installation

# install from PyPI
pip install m3ter

Usage

The full API of this library can be found in api.md.

import os
from m3ter import M3ter

client = M3ter(
    api_key="My API Key",
    api_secret="My API Secret",
    org_id="My Org ID",
    token=os.environ.get("M3TER_API_TOKEN"),  # This is the default and can be omitted
)

page = client.products.list()

While you can provide a token keyword argument, we recommend using python-dotenv to add M3TER_API_TOKEN="My Token" to your .env file so that your Token is not stored in source control.

Async usage

Simply import AsyncM3ter instead of M3ter and use await with each API call:

import os
import asyncio
from m3ter import AsyncM3ter

client = AsyncM3ter(
    api_key="My API Key",
    api_secret="My API Secret",
    org_id="My Org ID",
    token=os.environ.get("M3TER_API_TOKEN"),  # This is the default and can be omitted
)


async def main() -> None:
    page = await client.products.list()
    print(page.data)


asyncio.run(main())

Functionality between the synchronous and asynchronous clients is otherwise identical.

With aiohttp

By default, the async client uses httpx for HTTP requests. However, for improved concurrency performance you may also use aiohttp as the HTTP backend.

You can enable this by installing aiohttp:

# install from PyPI
pip install m3ter[aiohttp]

Then you can enable it by instantiating the client with http_client=DefaultAioHttpClient():

import os
import asyncio
from m3ter import DefaultAioHttpClient
from m3ter import AsyncM3ter


async def main() -> None:
    async with AsyncM3ter(
        api_key="My API Key",
        api_secret="My API Secret",
        org_id="My Org ID",
        token=os.environ.get("M3TER_API_TOKEN"),  # This is the default and can be omitted
        http_client=DefaultAioHttpClient(),
    ) as client:
        page = await client.products.list()
        print(page.data)


asyncio.run(main())

Using types

Nested request parameters are TypedDicts. Responses are Pydantic models which also provide helper methods for things like:

• Serializing back into JSON, model.to_json()
• Converting to a dictionary, model.to_dict()

Typed requests and responses provide autocomplete and documentation within your editor. If you would like to see type errors in VS Code to help catch bugs earlier, set python.analysis.typeCheckingMode to basic.

Pagination

List methods in the M3ter API are paginated.

This library provides auto-paginating iterators with each list response, so you do not have to request successive pages manually:

from m3ter import M3ter

client = M3ter(
    api_key="My API Key",
    api_secret="My API Secret",
    org_id="My Org ID",
)

all_products = []
# Automatically fetches more pages as needed.
for product in client.products.list():
    # Do something with product here
    all_products.append(product)
print(all_products)

Or, asynchronously:

import asyncio
from m3ter import AsyncM3ter

client = AsyncM3ter(
    api_key="My API Key",
    api_secret="My API Secret",
    org_id="My Org ID",
)


async def main() -> None:
    all_products = []
    # Iterate through items across all pages, issuing requests as needed.
    async for product in client.products.list():
        all_products.append(product)
    print(all_products)


asyncio.run(main())

Alternatively, you can use the .has_next_page(), .next_page_info(), or .get_next_page() methods for more granular control working with pages:

first_page = await client.products.list()
if first_page.has_next_page():
    print(f"will fetch next page using these details: {first_page.next_page_info()}")
    next_page = await first_page.get_next_page()
    print(f"number of items we just fetched: {len(next_page.data)}")

# Remove `await` for non-async usage.

Or just work directly with the returned data:

first_page = await client.products.list()

print(f"next page cursor: {first_page.next_token}")  # => "next page cursor: ..."
for product in first_page.data:
    print(product.id)

# Remove `await` for non-async usage.

Nested params

Nested parameters are dictionaries, typed using TypedDict, for example:

from m3ter import M3ter

client = M3ter(
    api_key="My API Key",
    api_secret="My API Secret",
    org_id="My Org ID",
)

account_response = client.accounts.create(
    code='S?oC"$]C] ]]]]]5]',
    email_address="[e-mail]",
    name="x",
    address={},
)
print(account_response.address)

Handling errors

When the library is unable to connect to the API (for example, due to network connection problems or a timeout), a subclass of m3ter.APIConnectionError is raised.

When the API returns a non-success status code (that is, 4xx or 5xx response), a subclass of m3ter.APIStatusError is raised, containing status_code and response properties.

All errors inherit from m3ter.APIError.

import m3ter
from m3ter import M3ter

client = M3ter(
    api_key="My API Key",
    api_secret="My API Secret",
    org_id="My Org ID",
)

try:
    client.products.list()
except m3ter.APIConnectionError as e:
    print("The server could not be reached")
    print(e.__cause__)  # an underlying Exception, likely raised within httpx.
except m3ter.RateLimitError as e:
    print("A 429 status code was received; we should back off a bit.")
except m3ter.APIStatusError as e:
    print("Another non-200-range status code was received")
    print(e.status_code)
    print(e.response)

Error codes are as follows:

Status Code	Error Type
400	BadRequestError
401	AuthenticationError
403	PermissionDeniedError
404	NotFoundError
422	UnprocessableEntityError
429	RateLimitError
>=500	InternalServerError
N/A	APIConnectionError

Retries

Certain errors are automatically retried 2 times by default, with a short exponential backoff. Connection errors (for example, due to a network connectivity problem), 408 Request Timeout, 409 Conflict, 429 Rate Limit, and >=500 Internal errors are all retried by default.

You can use the max_retries option to configure or disable retry settings:

from m3ter import M3ter

# Configure the default for all requests:
client = M3ter(
    api_key="My API Key",
    api_secret="My API Secret",
    org_id="My Org ID",
    # default is 2
    max_retries=0,
)

# Or, configure per-request:
client.with_options(max_retries=5).products.list()

Timeouts

By default requests time out after 1 minute. You can configure this with a timeout option, which accepts a float or an httpx.Timeout object:

from m3ter import M3ter

# Configure the default for all requests:
client = M3ter(
    api_key="My API Key",
    api_secret="My API Secret",
    org_id="My Org ID",
    # 20 seconds (default is 1 minute)
    timeout=20.0,
)

# More granular control:
client = M3ter(
    api_key="My API Key",
    api_secret="My API Secret",
    org_id="My Org ID",
    timeout=httpx.Timeout(60.0, read=5.0, write=10.0, connect=2.0),
)

# Override per-request:
client.with_options(timeout=5.0).products.list()

On timeout, an APITimeoutError is thrown.

Note that requests that time out are retried twice by default.

Advanced

Logging

We use the standard library logging module.

You can enable logging by setting the environment variable M3TER_LOG to info.

$ export M3TER_LOG=info

Or to debug for more verbose logging.

How to tell whether None means null or missing

In an API response, a field may be explicitly null, or missing entirely; in either case, its value is None in this library. You can differentiate the two cases with .model_fields_set:

if response.my_field is None:
  if 'my_field' not in response.model_fields_set:
    print('Got json like {}, without a "my_field" key present at all.')
  else:
    print('Got json like {"my_field": null}.')

Accessing raw response data (e.g. headers)

The "raw" Response object can be accessed by prefixing .with_raw_response. to any HTTP method call, e.g.,

from m3ter import M3ter

client = M3ter(
    api_key="My API Key",
    api_secret="My API Secret",
    org_id="My Org ID",
)
response = client.products.with_raw_response.list()
print(response.headers.get('X-My-Header'))

product = response.parse()  # get the object that `products.list()` would have returned
print(product.id)

These methods return an APIResponse object.

The async client returns an AsyncAPIResponse with the same structure, the only difference being awaitable methods for reading the response content.

.with_streaming_response

The above interface eagerly reads the full response body when you make the request, which may not always be what you want.

To stream the response body, use .with_streaming_response instead, which requires a context manager and only reads the response body once you call .read(), .text(), .json(), .iter_bytes(), .iter_text(), .iter_lines() or .parse(). In the async client, these are async methods.

with client.products.with_streaming_response.list() as response:
    print(response.headers.get("X-My-Header"))

    for line in response.iter_lines():
        print(line)

The context manager is required so that the response will reliably be closed.

Making custom/undocumented requests

This library is typed for convenient access to the documented API.

If you need to access undocumented endpoints, params, or response properties, the library can still be used.

Undocumented endpoints

To make requests to undocumented endpoints, you can make requests using client.get, client.post, and other http verbs. Options on the client will be respected (such as retries) when making this request.

import httpx

response = client.post(
    "/foo",
    cast_to=httpx.Response,
    body={"my_param": True},
)

print(response.headers.get("x-foo"))

Undocumented request params

If you want to explicitly send an extra param, you can do so with the extra_query, extra_body, and extra_headers request options.

Undocumented response properties

To access undocumented response properties, you can access the extra fields like response.unknown_prop. You can also get all the extra fields on the Pydantic model as a dict with response.model_extra.

Configuring the HTTP client

You can directly override the httpx client to customize it for your use case, including:

• Support for proxies
• Custom transports
• Additional advanced functionality

import httpx
from m3ter import M3ter, DefaultHttpxClient

client = M3ter(
    api_key="My API Key",
    api_secret="My API Secret",
    org_id="My Org ID",
    # Or use the `M3TER_BASE_URL` env var
    base_url="http://my.test.server.example.com:8083",
    http_client=DefaultHttpxClient(
        proxy="http://my.test.proxy.example.com",
        transport=httpx.HTTPTransport(local_address="0.0.0.0"),
    ),
)

You can also customize the client on a per-request basis by using with_options():

client.with_options(http_client=DefaultHttpxClient(...))

Managing HTTP resources

By default the library closes underlying HTTP connections whenever the client is garbage collected. You can manually close the client using the .close() method if desired, or with a context manager that closes when exiting.

from m3ter import M3ter

with M3ter(
    api_key="My API Key",
    api_secret="My API Secret",
    org_id="My Org ID",
) as client:
  # make requests here
  ...

# HTTP client is now closed

Versioning

This package generally follows SemVer conventions, though certain backwards-incompatible changes may be released as minor versions:

1. Changes that only affect static types, without breaking runtime behavior.
2. Changes to library internals which are technically public but not intended or documented for external use. (Please open a GitHub issue to let us know if you are relying on such internals.)
3. Changes that we do not expect to impact the vast majority of users in practice.

We take backwards-compatibility seriously and work hard to ensure you can rely on a smooth upgrade experience.

We are keen for your feedback; please open an issue with questions, bugs, or suggestions.

Determining the installed version

If you've upgraded to the latest version but aren't seeing any new features you were expecting then your python environment is likely still using an older version.

You can determine the version that is being used at runtime with:

import m3ter
print(m3ter.__version__)

Requirements

Python 3.9 or higher.

Contributing

See the contributing documentation.