ProfileOut Python SDK
Official synchronous Python client for the ProfileOut API.
Requires Python 3.10 or newer. No runtime dependencies.
Install
pip install profileout
Quick start
Get an API key from the ProfileOut console. The account must be active and email-verified, with sufficient credits.
import os
from profileout import ProfileOut
client = ProfileOut(api_key=os.environ["PROFILEOUT_API_KEY"])
request = client.create_people_data({"linkedin_id": "example-person"})
response = (
request if request["status"] in ("completed", "failed")
else client.wait_for_people_data(request["request_id"])
)
if response["status"] == "failed":
print(response.get("error"))
else:
print(response["result"])
Responses are dictionaries with the API's original snake_case fields. Nested profile fields can vary.
APIs
| Operation | Method |
|---|---|
| Submit / read a profile | create_people_data(input) / get_people_data(request_id) |
| Download profile image | get_people_data_image(request_id) → bytes |
| Upload / read a resume | create_profile_parsing(path) / get_profile_parsing(request_id) |
| Submit / read contact enrichment | create_contact_enrichment(input) / get_contact_enrichment(request_id) |
| Start / continue a search | create_people_search({"message": ...}) / continue_people_search(session_id, {"message": ...}) |
| Read a search | get_people_search(session_id) |
| Check service health | get_health() (does not send the API key) |
People Data and Contact Enrichment accept exactly one identity form:
{"linkedin_id": "example-person"}
{"profile_url": "https://www.linkedin.com/in/example-person"}
{"platform": "github", "account_id": "example-person"}
Platforms: linkedin, github, x, twitter, facebook. Facebook numeric IDs must be strings.
Resume upload
from pathlib import Path
request = client.create_profile_parsing(Path("resume.pdf"))
response = client.wait_for_profile_parsing(request["request_id"])
print(response["status"], response["result"], response.get("error"))
Accepts a filesystem path, reads at most 10 MiB plus one byte to check the limit, and sends exactly one multipart file field. Files must be nonempty PDF, PNG, JPEG, or TIFF with a matching extension; the service validates the file signature.
Search conversation
session = client.create_people_search({"message": "Find senior backend engineers in Seoul."})
response = client.wait_for_people_search(session["session_id"])
print(response["status"], response["follow_up"], response["role_summary"], response["filters"])
# After reviewing the response, optionally send a new paid revision:
revision = client.continue_people_search(session["session_id"], {"message": "Require Python experience."})
print(revision["revision"])
Wait methods read the current request/session state; they do not pin a search revision. Avoid concurrently updating a session while waiting for a particular revision.
Polling, errors, and timeouts
wait_for_people_data, wait_for_profile_parsing, wait_for_contact_enrichment, and wait_for_people_search accept an ID. They wait at least five seconds before the first GET and between pending results, honor longer next_poll_after_seconds hints, and return on either completed or failed. Always inspect status; HTTP 200 can contain a failed job, and search outputs can contain their own errors.
client = ProfileOut(api_key=os.environ["PROFILEOUT_API_KEY"], timeout=120)
response = client.wait_for_people_data(request_id, timeout=1800)
Timeout values use seconds. The client default is a 120-second timeout for blocking network operations. Wait methods default to a 20-minute polling deadline and cap each request's socket timeout by the remaining time. Python's standard HTTP transport uses a per-operation socket timeout; a slowly streaming response can overrun the polling deadline until that read finishes. A wait deadline raises TimeoutError. Local timeouts or interruption do not cancel processing on the server. This client is synchronous; calls block the calling thread.
from profileout import ProfileOutError
try:
response = client.get_people_data(request_id)
print(response["status"])
except ProfileOutError as error:
print(error.status, error.code, error.request_id)
# error.body contains the response; error.headers includes retry-after if present.
HTTP failures and invalid response objects raise ProfileOutError. Network errors use the standard library's urllib.error.URLError, OSError, or HTTP exceptions; invalid local inputs raise ValueError or TypeError.
No requests are automatically retried. Each accepted POST, including repeated submissions and search revisions, can reserve credits. After an ambiguous failure, recover a known request ID and use GET instead of blindly repeating POST. GET polling does not reserve additional credits. See billing.
The optional base_url defaults to https://api.profileout.com. HTTPS is required except on localhost; redirects are rejected so credentials and paid requests cannot be forwarded.
API compatibility
Targets the ProfileOut v1 public API. When that contract changes, review both SDKs against the service's OpenAPI specification and update methods and examples together.
License
MIT. The license covers SDK code; API access and credits are provided separately by ProfileOut.
Metadata
Release files for profileout 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| profileout-0.1.2.tar.gz | 7.5 kB | With provenance | Details for profileout-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| profileout-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for profileout-0.1.2-py3-none-any.whl |
Total release size: 15.2 kB
Release files / profileout-0.1.2.tar.gz
| Download URL | profileout-0.1.2.tar.gz |
|---|---|
| Size | 7.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9df3bec43c37ed9b28c1d044ab53163e90c08af49b6860001a5bc56af77785f9
|
|
BLAKE2b-256 checksum How to use checksums |
a444a53734ea7635b4dee891e488cc4f25483fa3a4f54f55feb8fdf0119d0279
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / profileout-0.1.2-py3-none-any.whl
| Download URL | profileout-0.1.2-py3-none-any.whl |
|---|---|
| Size | 7.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
21791d4f50270bad3fcc08950da67bffdf6160c7d235ef7e27a4de01abcffd1e
|
|
BLAKE2b-256 checksum How to use checksums |
276906dd5e2045a5a61672f4547164d768b8168c2e25dddaebcffd046f5ed4b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logSecurity for profileout 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for profileout-0.1.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.