pinarkive-sdk-py 3.1.1

Python SDK for PinArkive API v3 – minimal client (upload, pin, remove, users/me, uploads, tokens, status, allocations). See https://pinarkive.com/docs.php

Pinarkive Python SDK

Minimal Python client for the PinArkive API v3. Upload files, pin by CID, manage tokens, and check status. See pinarkive.com/docs.php.

Version: 3.1.1

Installation

pip install pinarkive-sdk-py

Quick Start

from pinarkive_client import PinarkiveClient, PinarkiveError

# Auth: Bearer token or X-API-Key (default base URL: https://api.pinarkive.com/api/v3)
client = PinarkiveClient(api_key="your-api-key-here")

# Upload a file
result = client.upload_file("document.pdf")
print(result["cid"])

# Or login first
login = client.login("[e-mail]", "password")
client = PinarkiveClient(token=login["token"])

# List uploads
data = client.list_uploads(page=1, limit=20)
print(data["uploads"])

Authentication

• API Key: PinarkiveClient(api_key="...") — sent as X-API-Key header.
• JWT: PinarkiveClient(token="...") — sent as Authorization: Bearer <token>.
• Base URL: optional third argument, default https://api.pinarkive.com/api/v3.
• request_source: optional keyword argument. When set to "web", the client sends X-Request-Source: web on every Bearer-authenticated request (not when using API Key), so the backend classifies them as WEB in logs instead of JWT. Use this when the SDK runs from a web app.

API Methods (minimal set)

Method	Description
health()	GET /health
get_plans()	GET /plans/
get_peers()	GET /peers/
login(email, password)	POST /auth/login
verify_2fa_login(temporary_token, code)	POST /auth/2fa/verify-login
upload_file(path, cluster_id=None, timelock=None)	POST /files/
upload_directory(dir_path, cluster_id=None, timelock=None)	POST /files/directory
upload_directory_dag(files_dict, dir_name=None, cluster_id=None, timelock=None)	POST /files/directory-dag
pin_cid(cid, original_name=None, custom_name=None, cluster_id=None, timelock=None)	POST /files/pin/:cid
remove_file(cid)	DELETE /files/remove/:cid
get_me()	GET /users/me
list_uploads(page=1, limit=20)	GET /users/me/uploads
generate_token(name, label=None, expires_in_days=None, scopes=None, totp_code=None)	POST /tokens/generate
list_tokens()	GET /tokens/list
revoke_token(name, totp_code=None)	DELETE /tokens/revoke/:name
get_status(cid, cluster_id=None)	GET /status/:cid
get_allocations(cid, cluster_id=None)	GET /allocations/:cid

Optional cluster_id and timelock (ISO 8601, premium) follow the API docs.

Error handling

On HTTP 4xx/5xx the client raises PinarkiveError with:

• status_code — HTTP status (400, 401, 403, 404, 409, 413, 429, 500, 503)
• message — from API message or error
• body — full JSON body
• .error — API field error
• .code — API field code (e.g. email_not_verified, missing_scope)
• .required — for 403 missing_scope: the required scope
• .retry_after — for 429: seconds until retry (from body or Retry-After header)

try:
    client.upload_file("large.bin")
except PinarkiveError as e:
    print(e.status_code, e.message, e.code)

Changelog

3.1.0

• Request source: request_source="web" sends X-Request-Source: web on Bearer requests.
• Scopes & 2FA: generate_token(..., scopes=..., totp_code=...); revoke_token(name, totp_code=...). verify_2fa_login(temporary_token, code) for login with 2FA.
• Errors: PinarkiveError.required (403 missing_scope), PinarkiveError.retry_after (429).

3.1.1

• Fix: upload_directory_dag now sends multipart with repeated field name files, with each part’s filename equal to the relative path in the DAG (backend multer upload.array('files')). The previous files[i][path] / files[i][content] format is not accepted by the backend.

See also CHANGELOG.md.

3.0.0

• API v3: Base URL is now https://api.pinarkive.com/api/v3 (was /api/v2). v1/v2 are deprecated (410).
• Errors: On 4xx/5xx the client raises PinarkiveError with status_code, message, body, and .error / .code from the API (no raw Response on failure).
• Minimal surface: Only endpoints documented at pinarkive.com/docs.php: health, plans, peers, login, files (upload, directory, directory-dag, pin, remove), users/me, uploads, tokens (generate with name / label / expiresInDays), status, allocations. Optional cluster_id and timelock (ISO 8601) on upload/pin.
• Removed: rename_file; token options permissions, ip_allowlist. Use API label and expiresInDays only.
• Pin: pin_cid now accepts original_name, custom_name (replacing the old filename).
• Return values: Successful calls return decoded JSON (dict); methods that return nothing on success (remove_file, revoke_token) return None.

Upgrading from 2.x

1. Change base URL to /api/v3 or rely on the new default.
2. Replace result.json() with the direct return value (client returns dicts; on error, PinarkiveError is raised).
3. Catch PinarkiveError instead of requests.HTTPError and use e.status_code, e.message, e.body.
4. Use pin_cid(cid, custom_name=...) instead of pin_cid(cid, filename=...); add original_name if needed.
5. Use generate_token(name, label=..., expires_in_days=...); drop permissions and ip_allowlist.
6. Pin to pinarkive-sdk-py>=3.0.0 if you rely on v3 behaviour.

Links

• API docs
• Repository