How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Lone Wolf Technologies Transactions API

Represents a transaction.

Lone Wolf Technologies Transactions API is one of 65 APIs that Lone Wolf Technologies publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transaction. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a changelog, and authentication docs.

This API exposes 23 operations across 14 paths, and defines 52 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 7 base URLs: https://api.lwolf.com/backoffice, https://gateway.lwolf.com, {tw_host}, https://api.globalwolfweb.com, https://api-sb.globalwolfweb.com, https://ws.zipformplus.com/api, https://api.pre.zipformplus.com/api.

23 operations 14 paths 52 schemas 2 DELETE11 GET2 PATCH6 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://gateway.lwolf.com
Authentication
HTTP Bearer, API Key, API Key, API Key, API Key, API Key
Resource Areas
1

Authentication & Security 6

Lone Wolf Technologies Transactions API declares 6 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). An API key is passed in the header as lw-subscription-key (subscriptionKey). An API key is passed in the header as Authorization (LoneWolfToken). An API key is passed in the header as X-Auth-ContextId (contextAuth). An API key is passed in the header as X-Auth-SharedKey (sharedKey). An API key is passed in the header as X-Auth-ExternalId (externalIdAuth).

  • bearerAuth — JWT access token obtained from the /oauth/token endpoint, sent as Authorization: Bearer .
  • subscriptionKey — API subscription key issued by Lone Wolf, sent on every request.
  • LoneWolfToken — Custom HMAC-signed authorization scheme used when calling resources that access your actual data: Authorization: LoneWolfToken [API Token]:[Client Code]:[Signa…
  • contextAuth — Context Id obtained from an authentication endpoint. Must be used together with X-Auth-SharedKey.
  • sharedKey — Shared Key provided by zipLogix to authenticate the partner application.
  • externalIdAuth — External Id for partners authorized to use the External Id authentication scheme. Must be used together with X-Auth-SharedKey.

Paths & Operations 23

Across 14 paths, the API surfaces 23 operations — 2 DELETE, 11 GET, 2 PATCH, 6 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Transactions 23

Represents a transaction.

GET
/v1/transactions
Get Transactions
get-v1-transactions → 200400401403
POST
/v1/transactions
Create Transaction
post-v1-transactions body → 200201400401403409422
GET
/v1/transactions/{transactionId}
Get Transaction
get-v1-transactions-transactionid 1 param → 200400401403404
PATCH
/v1/transactions/{transactionId}
Update Transaction
patch-v1-transactions-transactionid 1 param body → 200400401403404422
GET
/v1/transactions/{transactionId}/summary
Get Transaction Summary
get-v1-transactions-transactionid-summary 1 param → 200400401403404
GET
/v1/transactions/summary
Get Transaction Summaries
get-v1-transactions-summary → 200400401403
POST
/transact-workflow/v1/Transactions
Create a transaction
createTransaction body → 201400401403404
GET
/transact-workflow/v1/users/{userId}/transactions
List transactions
getTransactions 2 params → 200400401403404
GET
/transact-workflow/v1/users/{userId}/transactions/{transactionId}
Get a transaction
getTransactionByKey 2 params → 200400401403404
PATCH
/transact-workflow/v1/users/{userId}/transactions/{transactionId}
Update a transaction
updateTransaction 2 params body → 200400401403404
DELETE
/transact-workflow/v1/users/{userId}/transactions/{transactionId}
Delete a transaction
deleteTransaction 2 params → 204400401403404
GET
/wolfconnect/transactions/v1
Retrieve a Collection of Transactions
getTransactions 5 params → 200
POST
/wolfconnect/transactions/v1
Create a Transaction
createTransaction 1 param body → 201400404
GET
/wolfconnect/transactions/v1/{transactionId}
Retrieve a Transaction
getTransaction 2 params → 200400404
PUT
/wolfconnect/transactions/v1/{transactionId}
Update a Transaction
updateTransaction 2 params body → 200400404
PUT
/wolfconnect/transactions/v1/{transactionId}/finalize
Finalize a Transaction
finalizeTransaction 1 param body → 200400404
POST
/wolfconnect/transactions/v1/searchdeprecated
Search for Transactions
searchTransactions body → 200
GET
/transactions
Get Transaction List
10 params → 200401
POST
/transactions
Create Transaction
body → 201401
GET
/transactions/{transactionId}
Get Transaction Metadata
1 param → 200401404
DELETE
/transactions/{transactionId}
Delete Transaction
1 param → 200401404
GET
/transactions/{transactionId}/data
Get Transaction Data
1 param → 200401404
POST
/transactions/{transactionId}/data
Set Transaction Data
2 params body → 200401404

Schemas 52

The contract defines 52 schemas that model the data the API accepts and returns. The most detailed are Transaction (30 properties), ClientContact_2 (28 properties), TransactionBase (27 properties), Transaction_2 (24 properties). Each schema is shown below with its type and property counts.

ExternalAgent
object
Represents an agent involved in the transaction that does not work for the brokerage.
20 properties 4 required
TransactionPatchRequest
object
Used to patch properties of a condition.
19 properties
Transaction
object
Represents a transaction.
30 properties
CommissionFee
object
Represents a fee that is related to a commission.
10 properties
ContactTypeReadOnly
object
A read only representation of a contact type.
2 properties
ClassificationReadOnly
object
A read only representation of a transaction classification.
4 properties
ClientContact
object
Represents a buyer or seller on a transaction. For companies or business contacts, see Business Contact.
22 properties 4 required
Condition
object
Represents a condition on a transaction.
6 properties 2 required
EmployeeReadOnly
object
A read only representation of an agent.
3 properties
Commission
object
Represents a commission for an agent on a transaction.
16 properties 3 required
OfficeReadOnly
object
A read only representation of an office.
2 properties
BusinessContact
object
Represents a company or business contact like a Lawyer or Title Company. See client contacts for buyers and sellers.
22 properties 4 required
Tier
object
Represents a sub transaction.
17 properties 1 required
TierSummary
object
Represents a summary of a tier in a transaction.
5 properties
ApiError
object
4 properties
FeeReadOnly
object
A read only representation of a fee associated with a transaction.
2 properties
Deposit
object
Represents a deposit associated to a transaction.
11 properties 2 required
CommissionSummary
object
A summary of the commission for an agent.
13 properties
TransactionSummary
object
Represents a summary of a transaction.
23 properties
ExternalCommission
object
Represents a commission paid to an external agent involved in a transaction.
10 properties 2 required
PropertyTypeReadOnly
object
A read only representation of a property type.
5 properties
TransactionCreate
Payload for creating a new transaction.
TransactionBase
object
27 properties
TransactionUpdate
Partial transaction representation. Only the provided fields are updated.
Error
object
2 properties
ExternalAgent_2
object
16 properties 3 required
PropertyType
object
8 properties
Task
object
Tasks cannot currently be updated by the Transactions API. They will be ignored in any resource call to create or update a transaction.
10 properties
Agent
object
5 properties
Transaction_2
object
24 properties 7 required
NumericRange
object
2 properties
SearchOrder
object
2 properties
EmailAddress
object
5 properties 2 required
PhoneNumber
object
6 properties 2 required
ClientContact_2
object
28 properties 1 required
TransactionCondition
object
A condition attached to a transaction. Note: this differs from the Condition lookup object returned by the Conditions API. Please see the Creating and Updating…
7 properties 1 required
BusinessContact_2
object
17 properties 2 required
Tier_2
object
16 properties 4 required
MLSAddress
object
10 properties 6 required
Address
object
13 properties 6 required
ExternalAgentCommission
object
9 properties 3 required
SearchResult
object
Paging is currently not implemented. Therefore PageSize will always be the number of objects in the ResultSet and TotalPages will always be 1. Write your clien…
6 properties
TransactionSearchCriteria
object
16 properties
SearchRequest
object
3 properties 1 required
TimestampRange
object
The TimestampRange object is used to compare Timestamp fields, not Date fields. To compare Date fields, use DateRange.
2 properties
AgentCommission
object
13 properties 4 required
ClientError
object
The ClientError object is used to give detailed information whenever an API request fails. If you perform a request that returns with an error and the response…
3 properties
Classification
object
6 properties
DateRange
object
The DateRange object is used to compare Date fields, not Timestamp fields. To compare Timestamp fields, use TimestampRange.
2 properties
SourceOfBusiness
object
5 properties
ContactType
object
6 properties
Transaction_3
object
20 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lone-wolf-transactions-api-openapi.yml Raw ↑

Other APIs Lone Wolf Technologies publishes across the network.

Lone Wolf Authentisign API
Lone Wolf Technologies Accounts API
Lone Wolf Technologies Authentication API
Lone Wolf Technologies Authorization API
Lone Wolf Technologies Business Contact API
Lone Wolf Technologies Business Contacts API
Lone Wolf Technologies C Cs API
Lone Wolf Technologies Classification API
Lone Wolf Technologies Classifications API
Lone Wolf Technologies Client Contact API
Lone Wolf Technologies Client Contacts API
Lone Wolf Technologies Commission API
Where this information came from

This is an independent, third-party profile of Lone Wolf Technologies Transactions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.