python-eloqua-wrapper
This outlines the current behavior and use cases of the API via an example.
Functionality includes creating, updating, or deleting Custom Data Object records in Eloqua, and creating, retrieving, or deleting Contacts in Eloqua.
Example Outline
Let's say we have a CDO with ID# 12345, and a record with these field values:
Record ID#369789
- business_email: bob@bobbyworld.com
- first_last_name: bob_wilbert
- zip_code: 32123
- job_title: Nannygoat Herder
We would like to update him in our CDO with the following:
- zip_code: 22667
- job_title: Alligator Wrangler
How do we upload changes via our lovely api wrapper?
Step 1: What you need to upload data to Eloqua
To push a given record with the basic CdoRecord class, you will need:
- the CDO ID
- the CDO record ID
- A dictionary of the fieldName:value pairs you want to upload/update
- A dictionary of the fieldName:fieldID pairs to map your fieldsNames
Step 2: bare bones initialization
from python_eloqua_wrapper.cdo_record import CdoRecord
from python_eloqua_wrapper.eloqua_session import EloquaSession
from os import environ
session = EloquaSession(company=environ["ELOQUA_COMPANY"],
username=environ["ELOQUA_USER"],
password=environ["ELOQUA_PASSWORD"])
cdo_record = CdoRecord(session=session)
That's it, you now have a local object!
Step 3: Updating your record
There is a method called update_cdo_record, which can be used as follows:
cdo_record.update_cdo_record(
cdo_id=12345,
record_id=369789,
cdo_field_to_field_id_map={
'zip_code': 11221,
'job_title': 11232},
record_fields_and_values_dict={
'zip_code': '22667',
'job_title': 'Alligator Wrangler'})
Simply execute this and you will receive the response object if it was successful, else it will raise an exception.
To be more explicit about update behavior:
- If a previous value for that field/column already existed: it gets overwritten.
- If you don't provide a field/column name, it won't alter that column.
Metadata
Release files for python-eloqua-wrapper 0.0.9
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 |
|---|---|---|---|---|
| python_eloqua_wrapper-0.0.9.tar.gz | 8.8 kB | Without provenance | Details for python_eloqua_wrapper-0.0.9.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| python_eloqua_wrapper-0.0.9-py3-none-any.whl | Python 3 | none | any | Details for python_eloqua_wrapper-0.0.9-py3-none-any.whl |
Total release size: 18.2 kB
Release files / python_eloqua_wrapper-0.0.9.tar.gz
| Download URL | python_eloqua_wrapper-0.0.9.tar.gz |
|---|---|
| Size | 8.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
14337898e8ac6ce7217ce285618c0643b0ddacf682ce514633b385c38ff7e9f6
|
|
BLAKE2b-256 checksum How to use checksums |
b5c0e3b30a8b8068847d04dfb35bc6b74626276ef0d047a09dc7b21a4c3d5141
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.10.0 pkginfo/1.8.2 requests/2.27.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.10
|
Release files / python_eloqua_wrapper-0.0.9-py3-none-any.whl
| Download URL | python_eloqua_wrapper-0.0.9-py3-none-any.whl |
|---|---|
| Size | 9.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7e93cde016854414f9efa91ddf5486b5f471c72ba89643ef227d9eeefb039560
|
|
BLAKE2b-256 checksum How to use checksums |
d5ecd245f76529e599854ed714dac4147a8942c80e45824dcc2df87d7b6cf8f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.10.0 pkginfo/1.8.2 requests/2.27.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.10
|
Security for python-eloqua-wrapper 0.0.9
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.