Personal Payment Methods
personalPaymentMethods Based on latest (2026.09)
Create, change, delete and look up Personal Payment Methods.
The record key personalPaymentMethodsUniqID is a generated hash. Take it from the record's links (rel self) in a GET response; never build it yourself.
Oracle documents an Effective-Of header and an effectiveDate parameter for this resource, used for date-effective reads and changes.
- Operations
- GET (list)GET (one)POST (create)PATCH (update)DELETE
- Record key
personalPaymentMethodsUniqID- Required on create
- none marked
- At a glance
- 13 fields1 finders0 children
- Extra parameters
?effectiveDate=Effective-Of:
Try it
Only attributes Oracle marks as searchable are offered.
GET /hcmRestApi/resources/11.13.18.05/personalPaymentMethods?fields=Amount,BankAccountId,EffectiveEndDate,EffectiveStartDate,Name&limit=25&onlyData=true
{
"items": [
{
"Amount": 0,
"BankAccountId": 0,
"EffectiveEndDate": "2026-01-31",
"EffectiveStartDate": "2026-01-31",
"Name": "<string, max 250>"
}
],
"count": 25,
"hasMore": true,
"limit": 25,
"offset": 0
}Shapes and placeholders, not real data. Replace https://<your-pod> and the login with your own: this site never sees them. Based on Oracle's latest (2026.09) REST specification.
Fields 13
| Attribute | Type | Use |
|---|---|---|
Amount | number | Optional on createUpdatableSearchable |
BankAccountId | number | Optional on createUpdatableSearchable |
EffectiveEndDate | date | Optional on createUpdatableSearchable |
EffectiveStartDate | date | Optional on createUpdatableSearchable |
Name | text · max 250 | Optional on createUpdatableSearchable |
OrgPaymentMethodId | number | Optional on createUpdatableSearchable |
PartyId | number | Read-onlySearchable |
PaymentAmountType | text · max 30 | Optional on createUpdatableSearchable |
PayrollRelationshipId | number | Optional on createUpdatableSearchable |
Percentage | number | Optional on createUpdatableSearchable |
PersonNumber | text · max 30 | Read-onlySearchable |
PersonalPaymentMethodId | number | Optional on createSearchable |
Priority | number | Optional on createUpdatableSearchable |
Names, types, labels and flags from Oracle's REST specification (latest (2026.09)). Flexfield and custom attributes vary by pod: check /describe for yours.
Finders 1
Predefined searches: ?finder=Name;variable=value,variable2=value2. Pick one in Try it to build the call.
findByAssignmentNumberPersonNumber·AssignmentNumberPersonNumberSysEffectiveDate
Check a payload
Checked in your browser only; nothing you paste is sent anywhere. Checks names and flags, not values.
Use in AI Agent Studio
- Point a Business Object or REST tool at
/hcmRestApi/resources/11.13.18.05/personalPaymentMethodsand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - Prefer a finder such as
findByAssignmentNumberPersonNumberfor the agent's main search: its variables become clean tool parameters. - Narrow with
q=on searchable fields and a smalllimit; for a count usetotalResults=true&limit=1. - Call once and pass the result on to later steps rather than calling the same endpoint again.
- This resource can change data. Put a human approval step before any create, update, delete or action call.
More in For Builders.
Pitfalls
- Attribute names are case-sensitive in
q,fieldsand bodies:Amount, notamount. - 2 fields are read-only: sending them in POST or PATCH fails or is ignored. The builder leaves them out.
onlyData=trueremoveslinks, and this resource's key only comes fromlinks. Leave it off when you need the key.- Send dates as
YYYY-MM-DD; date-time fields take ISO 8601 with a time zone. - A list returns 25 rows unless you set
limit; readhasMoreand moveoffsetto page through. - Text fields have maximum lengths (shown in the field table). Longer values are rejected.