profile
viewpoint
Chris Corbyn d11wtq Melbourne, Australia

d11wtq/dockerpty 126

Pseudo-tty handler for docker Python client

d11wtq/gentoo-packer 72

Packer scripts to create a Gentoo Vagrant box

d11wtq/ctrlp_bdelete.vim 58

An extension to ctrlp.vim for deleting open buffers

d11wtq/dm-sql-finders 10

DataMapper SQL Finders

d11wtq/docker-ami-packer 10

Packer recipe for a docker-capable Amazon EC2 AMI

d11wtq/dm-master-slave-adapter 9

Master/Slave Adapter for DataMapper (for things like MySQL replication)

d11wtq/gentoo-vm 7

Dev environment using Gentoo Linux

d11wtq/apache-docker 6

Docker container for running Apache

d11wtq/dot-vim 6

My .vimrc configuration

d11wtq/clojure-docker 4

Docker container for running Clojure apps

startedjwt/ruby-jwt

started time in 20 hours

pull request commentjwt/ruby-jwt

Add support for JWKs with EC key type

Just a comment to say thank you so much for doing this. We need this functionality too and exploring the alternative JWT gems, I didn't like what I saw in some of the solutions. Would love to see this one get across the line. I'm happy to help in any way I can do too ❤️

richardlarocque

comment created time in 21 hours

starteddoorkeeper-gem/doorkeeper

started time in 12 days

issue commentup-banking/api

ETA for OAuth2?

Hi @drnic! OAuth is on the cards but at this point we can't give a firm timeframe on when it will be implemented. It will almost certainly be before any other Australian bank offers it outside of the CDR (Open Banking) though. We're using this period as an opportunity to better understand the potential use cases, take feedback and have the breathing space to innovate without being slowed down by the complexities of managing third-party access too early. The current phase is really a beta for enthusiasts to prove out the high level design of the API before we move into the next phase (being third party access).

In parallel with running this beta phase of our public API we are also working heavily on implementing the CDR (Open Banking), though obviously the audience for that and the style of the API is considerably different.

drnic

comment created time in 13 days

pull request commentConsumerDataStandardsAustralia/banking-products-comparator

Add Up to datasources.json.

Done 👍

d11wtq

comment created time in 20 days

PR opened ConsumerDataStandardsAustralia/banking-products-comparator

Add Up to datasources.json.

👋 Calling from Up! https://up.com.au/

⚡️ This adds Up to the list with our implementation of "Get Products" and "Get Product Detail".

+1 -0

0 comment

1 changed file

pr created time in 20 days

push eventup-banking/banking-products-comparator

d11wtq

commit sha 90eb89e214a9dafb2b52d1bcccf1d2bde7f611ce

Add Up to datasources.json. 👋 Calling from Up! https://up.com.au/ ⚡️ This adds Up to the list with our implementation of "Get Products" and "Get Product Detail".

view details

push time in 20 days

issue closedConsumerDataStandardsAustralia/standards-maintenance

Clarification on Paginated Responses to POST Requests (Get Balances for Specific Accounts)

Request For Clarification

https://consumerdatastandardsaustralia.github.io/standards/#get-balances-for-specific-accounts

On the endpoint POST /banking/accounts/balances, a request is received with a list of accountIds present in the payload. The response includes LinksPaginated, which implies it must therefore also be possible to GET balances for specific accounts.

Is it expected that:

  1. The client follows the pagination links by re-submitting the same POST but to the new URL; or
  2. The server implements a GET-compatible variant of the endpoint and refers to this in the links?

closed time in 21 days

d11wtq

issue commentConsumerDataStandardsAustralia/standards-maintenance

Clarification on Paginated Responses to POST Requests (Get Balances for Specific Accounts)

@nils-work Thanks, that makes sense. It's probably worth something added to the section on Pagination that explicitly states how pagination works on POST requests.

d11wtq

comment created time in 21 days

issue openedConsumerDataStandardsAustralia/standards-maintenance

Clarification on Paginated Responses to POST Requests (Get Balances for Specific Accounts)

Request For Clarification

https://consumerdatastandardsaustralia.github.io/standards/#get-balances-for-specific-accounts

On the endpoint POST /banking/accounts/balances, a request is received with a list of accountIds present in the payload. The response includes LinksPaginated, which implies it must therefore also be possible to GET balances for specific accounts.

Is it expected that:

  1. The client follows the pagination links by re-submitting the same POST but to the new URL; or
  2. The server implements a GET-compatible variant of the endpoint and refers to this in the links?

created time in 21 days

issue commentup-banking/api

Be able to add tags for payments (one off and scheduled) before the transactions is complete

Agree this would be super useful to have in the Up app.

gregless22

comment created time in 23 days

push eventup-banking/api

Andrew Macdonald

commit sha 72ae786f5366fd055cb35c91e7bba0c378590d42

Update EXAMPLES.md

view details

Andrew Macdonald

commit sha 221ad13ca5aa64d97ba8e01fb6f8905b25ba1273

Update EXAMPLES.md

view details

Chris Corbyn

commit sha e5b34d1624e9c63b1b16cd1ac8cf8dd3b8c7f7c7

Merge pull request #62 from SelectSystemsInternational/master Added a .Netcore SDK for the Up Bank Api

view details

push time in a month

PR merged up-banking/api

Added a .Netcore SDK for the Up Bank Api

This SDK was produced by manually creating all the classes by reading the online document and developer website. I modified another Api to incorporated the new data structures and then made some test routines. All endpoints in the Up Bank Api are supported. The SDK has been tested with my Up Bank account. I welcome any comments or if you find problems let me know.

Since finalising this version and coming to understand a lot more about swagger and auto code creation from an Open Specification I will revisit it and produce a new version.

I just found the openapi.json specification and loaded it into My Swagger Hub and generate a cSharp Client SDK but there was a bunch of errors when I loaded it into Visual Studio and tried to build it. Not sure if that is an error in the openapi.json or bugs in the swagger code generator. I will look into it all over time.

+10 -0

1 comment

1 changed file

SelectSystemsInternational

pr closed time in a month

PullRequestReviewEvent

pull request commentup-banking/api

Added a .Netcore SDK for the Up Bank Api

Thanks 🙇

I just found the openapi.json specification and loaded it into My Swagger Hub and generate a cSharp Client SDK but there was a bunch of errors when I loaded it into Visual Studio and tried to build it. Not sure if that is an error in the openapi.json or bugs in the swagger code generator.

What were the errors? It's possible the version of OpenAPI that it supports differs from what we're using. We validate our OpenAPI json against the official JSON schema for OpenAPI v3, so it's technically valid OpenAPI v3, but feel free to let us know what errors you're getting.

SelectSystemsInternational

comment created time in a month

issue commentCocoaPods/CocoaPods

Intermittent CDN issues

When going direct to netlify I notice that none of the cloudflare headers (e.g. cf-ray) are present. Is that significant in debugging this?

The presence of the Host header set to cdn.cocoapods.org seems to cause those headers to become present (and this issue to occur).

j-h-a

comment created time in a month

issue commentCocoaPods/CocoaPods

Status page doesn't monitor CDN

Yeah I found if you just curl the netlify URL directly but pass -H 'Host: cdn.cocoapods.org' it doesn't work, so I don't think it's the CNAME so much as how the Host header is being handled.

j-h-a

comment created time in a month

issue commentCocoaPods/CocoaPods

Status page doesn't monitor CDN

More on that:

curl -i -H 'Host: cdn.cocoapods.org' https://cocoapods-cdn.netlify.app/CocoaPods-version.yml

It looks like the Host header being set to cdn.cocoapods.org when calling the server running at cocoapods-cdn.netlify.app triggers the issue. I'm guessing this is just some conditional magic to route via the CDN based on the hostname.

j-h-a

comment created time in a month

issue commentCocoaPods/CocoaPods

Status page doesn't monitor CDN

Somebody within our team noticed that cdn.cocoapods.org is a CNAME for cocoapods-cdn.netlify.com, which redirects to cocoapods-cdn.netlify.app. If you curl https://cocoapods-cdn.netlify.app/ directly it works.

$ curl -i https://cocoapods-cdn.netlify.app/CocoaPods-version.yml
HTTP/2 200
accept-ranges: bytes
cache-control: public, max-age=0, must-revalidate
content-length: 61
content-type: application/x-yaml
date: Tue, 22 Sep 2020 05:55:27 GMT
strict-transport-security: max-age=31536000; includeSubDomains; preload
etag: "77181d6d2b122682dd950cfed6aae3e0-ssl"
age: 0
server: Netlify
x-nf-request-id: 6a6fc8c8-7430-4aa5-b8bd-c0afde0404b3-13920496

---
min: 1.0.0
last: 1.10.0.rc.1
prefix_lengths:
- 1
- 1
- 1

Whereas via the CNAME it fails with the "proxy cycle" error message.

j-h-a

comment created time in a month

issue commentCocoaPods/CocoaPods

Status page doesn't monitor CDN

We're seeing the CDN down for a couple of hours now too.

Going directly to cdn.cocoapods.org is returning:

Description: Could not process your request for the document because it would cause an HTTP proxy cycle. Please check the URL and your browser's proxy settings.

j-h-a

comment created time in a month

issue commentup-banking/api

Handle URL encoded square brackets in query params

TBH we can probably get better at rejecting unhandled query parameters (e.g. returning a 400, or putting some message in the metadata).

nick96

comment created time in a month

issue commentup-banking/api

Handle URL encoded square brackets in query params

In particular if you look at the links in a paginated response you'll see we URL encode these characters ourselves and those URLs definitely work as expected.

nick96

comment created time in a month

issue commentup-banking/api

Handle URL encoded square brackets in query params

@nick96 It does understand URL-encoded square brackets. Are you having a problem with a specific call?

nick96

comment created time in a month

issue commentup-banking/api

Add endpoint for statements

Thanks for the love @waynerobinson ❤️

What would you expect the endpoint to return? PDF data? A link to the PDF? Or structured data?

waynerobinson

comment created time in a month

issue closedup-banking/api

Certain emojis missing from displayName

Just noticed that when fetching a either a list of all accounts or a single account, if certain emojis are used for the Saver, then the displayName is returned with no emoji included.

Haven't tested exhaustively so don't know how widespread this is but after choosing 10 emojis at random, found that both 🤖 (robot) and 🧑‍🔧 (mechanic) don't work,

closed time in a month

joshmeney

issue commentup-banking/api

Certain emojis missing from displayName

We've defined a mapping that means this should now be fixed 🙇

joshmeney

comment created time in a month

issue commentup-banking/api

URL scheme on iOS

Good idea @iJas0n. Have raised for discussion internally ❤️ We'd have to release an app update to support this, as as you've noted the IDs in the API will not currently work with the app out of the box.

iJas0n

comment created time in a month

issue commentup-banking/api

Certain emojis missing from displayName

Thanks for the heads up @joshmeney. We store the emoji name itself and are using a library to get the actual emoji. On the app this is handled by the client side in both directions, so there's probably a gap between the two solutions, or simply we need to add some aliases. Will look into the ones you mentioned. Any others let us know and we can have a look too.

When we expose more detailed Saver info we'll likely expose the emoji name in addition to its Unicode character in a more structured fashion than we're doing here.

joshmeney

comment created time in 2 months

PullRequestReviewEvent

push eventup-banking/api

Nathan Dench

commit sha 3d2d49abef05588b1e759a142945fb558a08a615

Add TypeScript SDK to EXAMPLES.md

view details

Chris Corbyn

commit sha ecf0b6d7fbf27828c385411775ced10eadb902db

Merge pull request #54 from ndench/patch-1 Add TypeScript SDK to EXAMPLES.md

view details

push time in 2 months

PR merged up-banking/api

Add TypeScript SDK to EXAMPLES.md

I've written a TypeScript SDK to wrap the API, giving a little bit of type safety and IDE autocompletion :smile:

+10 -0

0 comment

1 changed file

ndench

pr closed time in 2 months

PullRequestReviewEvent

issue commentup-banking/api

Closed Savers

Closed savers is certainly something that has been considered. I think the fact you're getting the account info for transactions on closed Savers is an unexpected oversight in the data coming out of the API, but perhaps the best solution is just to provide the closed Saver. There may be some nuance around this, so we'll have to have a closer look into it 👀

gxander85

comment created time in 2 months

PR closed up-banking/api

Fix: Typo in transaction api

Quick typo fix.

+2 -2

1 comment

1 changed file

ndench

pr closed time in 2 months

pull request commentup-banking/api

Fix: Typo in transaction api

This has now been fixed upstream, thanks 🙇

ndench

comment created time in 2 months

IssuesEvent

issue closedup-banking/api

🚀 Up API Changelog

🚀 Changelog

Welcome to the Up API Changelog. This is where we'll provide updates to the community about the changes we make to the Up API. If you want to receive all updates to this changelog, click the "Subscribe" button in the Github sidebar.

<div align="center"> <h2> 👉 <img src="https://user-images.githubusercontent.com/37948/89483251-ed2bbe80-d7de-11ea-970c-62711b1bef7c.png" width="300" valign="middle" /> </h2> </div>

This issue will remain locked, but if you have questions or feedback about any of the changes—or if you're encountering an issue—please go ahead and create a new issue and we'll do our best to help.

<div align="center"><a alt="Jump to the latest changelog" href="https://github.com/up-banking/api/issues/31#issuecomment-678079981"><image src="https://user-images.githubusercontent.com/4755785/89597098-7f45cc80-d89c-11ea-8a47-113a47cce1c1.png" width="300" alt="Jump to the latest changelog" /></a></div>

closed time in 2 months

d11wtq

issue commentup-banking/api

🚀 Up API Changelog

d11wtq

comment created time in 2 months

push eventup-banking/api

d11wtq

commit sha d49df20f82a2de1444b08d87bb7999216721a666

Update OAS JSON to Latest Snapshot. Adds category filtering and minor copy changes.

view details

push time in 2 months

issue closedup-banking/api

Clarify Docs For roundUp.amount + roundUp.boostPortion

Our documentation for the two MoneyObject values beneath roundUp on TransactionResource is not very clear. The amount includes any boostPortion, but the docs do not make this clear.

image

The documentation for amount probably needs to change to say something along the lines of:

The total amount of this Round Up, including any boosts, represented as negative value.

closed time in 2 months

d11wtq

issue closedup-banking/api

Tagged Transactions

Is there a way to have the tags for transactions to appear as a comma separated value rather than a list then records for each? Multiple Tags generate multiple lines for the same transactions. I've done a manual work around via PowerQuery & Excel, but it's messy 😬

closed time in 2 months

gxander85

issue commentup-banking/api

Tagged Transactions

🙇

gxander85

comment created time in 2 months

PullRequestReviewEvent

issue closedup-banking/api

Attributes Missing

Hi, I have discovered an issue with calling on the API and only pulling the most recent batch of transactions. If an attribute has not been used, it does not exist in that specific call.

Example. Boost Round Ups are switched off within app. attributes.roundUp.boostPortion.currencyCode, attributes.roundUp.boostPortion.value, attributes.roundUp.boostPortion.valueInBaseUnits are all missing. This is not limited to just boostPortion. Any attribute that is not present in the call is not within the JSON strings.

This causes issues with matching columns to a full history. I am reworking a flow in Parabola and pulling in the full history from a Google Sheet and matching to updated transactions from a single 100page call. If the columns don't exist, I cannot match them up.

Can all attributes be present even if null? The result would just be blank, but column header would be present.

closed time in 2 months

gxander85

issue commentup-banking/api

Attributes Missing

That solution sounds like a good one to me, yeah 👍 Glad to heat you figured out a way.

gxander85

comment created time in 2 months

issue openedup-banking/api

Clarify Docs For roundUp.amount + roundUp.boostPortion

Our documentation for the two MoneyObject values beneath roundUp on TransactionResource is not very clear. The amount includes any boostPortion, but the docs do not make this clear.

image

The documentation for amount probably needs to change to say something along the lines of:

The total amount of this Round Up, including any boosts, represented as negative value.

created time in 2 months

issue commentup-banking/api

Attributes Missing

The best I can suggest is that you first normalize the data structure to place the nulls where you would like them, so e.g.

if (attributes.roundUp == null) {
  attributes.roundUp = {
    amount: {
      currencyCode: null,
      value: null,
      valueInBaseUnits: null
    },
    boostPortion: null
  };
}

if (attributes.roundUp.boostPortion == null) {
  attributes.roundUp.boostPortion = {
    currencyCode: null,
    value: null,
    valueInBaseUnits: null
  };
}

But it seems like potentially there's a better approach to solving this problem, by extracting the data you need from the response into a structure that makes sense for your use case, and then passing that extracted data into whatever your process is for handling the data.

gxander85

comment created time in 2 months

issue commentup-banking/api

Attributes Missing

I think with these kinds of issues where the payload does not map 1:1 with the software, you will probably need to transform the data structure before loading it in. I don't think I'd be a huge fan of something like:

"roundUp": {
  "amount": {
    "currencyCode": null,
    "value": null,
    "valueInBaseUnits": null
  },
  "boostPortion": {
    "currencyCode": null,
    "value": null,
    "valueInBaseUnits": null
  }
}

Now to work out if a transaction had a round up you need to deeply traverse the amount structure for a round up that never happened. It also means we'd have to document the MoneyObject type as having nullable fields everywhere (and presumably every object type's fields).

gxander85

comment created time in 2 months

issue commentup-banking/api

Attributes Missing

Hi @gxander85, the roundUp field itself is documented as nullable. What kind of object would we put in the field if there was no round-up? Similarly, the boostPortion on a round up is nullable, because if there's no boost what would we put there? I'm not clear what you're proposing would go in the fields in the case there's no round up.

At some point, you either have to choose not to return the field, or make it nullable. Not everything can have a value if there's no value associated with it.

Can you give a direct example of a payload and what you would want to change it to?

gxander85

comment created time in 2 months

issue closedup-banking/api

Account Reconciliation Variance

Hi Team, I have been having a lot of fun with the API and with the assistance of other Upsider via this repo I've been able to dump all transactions into excel using power query.

However, when reconciling the accounts summary totals, vs the transactions totals, there is a variances. I can see when I check some transfers, they result in a negative balance or an 1.E15 error in excel.

My variance seems to be consistent at $4.11 and I've been monitoring it as I make more purchases/transfers as I use my account.

I would be happy to share my document with devs to debug if needed.

Thanks!

closed time in 2 months

gxander85

issue commentup-banking/api

Account Reconciliation Variance

💬 Handling this via Talk to Us in app, so will close this off.

gxander85

comment created time in 2 months

push eventup-banking/api

d11wtq

commit sha 918be0acf871296effdaba9c7091606ceb828ea9

Update OAS JSON to Latest Snapshot. Minor tweaks to code examples for webhook authenticity checks.

view details

push time in 2 months

issue closedup-banking/api

PHP example in docs has issues

Noticed a couple of issues while implementing in Laravel.

  1. Using php://input is problematic for tests, and generally fails in older versions of PHP.
  2. If header is missing, hash_equals will throw an exception - better to use ?? '' to ensure variable is non-null.
  3. Trailing , in header() call

Revised code to address these issues:

public function handleWebhookEvent(Request $request, $hook) {
    $received_signature = $request->header(
        'X-Up-Authenticity-Signature'
    ) ?? '';
    $raw_body = $request->getContent();
    $signature = hash_hmac('sha256', $raw_body, $hook->secret_key);
    if (!hash_equals($signature, $received_signature)) {
        abort(401);
    }
    // Process webhook event
}

closed time in 2 months

aliask

issue commentup-banking/api

PHP example in docs has issues

Fix incoming 🚢

aliask

comment created time in 2 months

push eventup-banking/api

simbesh

commit sha b5c82a40e4f6c20cfbe639fd25303bd90d4cc70a

Update EXAMPLES.md

view details

Chris Corbyn

commit sha c6041a9d04a1439625ed10a58e16156ba97a9412

Merge pull request #50 from simbesh/master Update EXAMPLES.md

view details

push time in 2 months

PR merged up-banking/api

Update EXAMPLES.md

Add my demo 😀

+10 -0

0 comment

1 changed file

simbesh

pr closed time in 2 months

PullRequestReviewEvent

issue commentup-banking/api

PHP example in docs has issues

❤️ Thanks, will fix up the example. Trailing commas are fine, but looks like that was only added with PHP 7.3 so will take that out too.

aliask

comment created time in 2 months

issue commentup-banking/api

Resources for testing / demonstration

Hi @aliask! Glad you're enjoying the API. Agree a test environment would be very handy. Certainly not a small undertaking. While we're still in beta for personal access only, for now it'll just need to be a case of playing around with live data, but will leave this open as it's a great suggestion and good for visibility.

aliask

comment created time in 2 months

issue commentup-banking/api

Expose merchant domain for use with external API

❤️ Absolutely. This is planned. This is a partial duplicate of #19, which deals with merchants and physical location.

jakehwll

comment created time in 2 months

issue commentup-banking/api

Pretty Printed Key

This is one reason we expose the value, valueInBaseUnits along with the currencyCode (it maps nicely to money libraries designed to deal with currency), but providing a formatted example is certainly an interesting idea for use cases where the value isn't needed for any arithmetic type operations and purely for display 🤔

jakehwll

comment created time in 2 months

issue commentup-banking/api

Seperate Saver Emoji & Name from `displayName` field

Hi @jakehwll,

Yes, basically the plan (in the not too distant future) is to expose all the detailed/structured Saver details, which would include separating the name from the emoji. The accounts endpoint is much more of a summary endpoint; breakdown of details for specific account types will (most likely) be handled in an endpoint specific to that account type, so that, for example create/update type operations can pair symmetrically with the representation that is returned in the API.

jakehwll

comment created time in 2 months

issue commentup-banking/api

Tagged Transactions

❤️ No worries at all. I'd be happy to help solve the problem, but unfortunately I don't have access to a windows machine at the moment to test anything windows-specific. One thing I will say—but you're probably already aware—is that by representing tags as columns, you're in for a lot of columns and I'm not certain how it would work if different transactions use different tags.

As you mention, the rule is up to 6 tags per transaction, with up to 100 tags in total, so that's potentially 100 extra columns. If those columns need to be consistent from one row to the next then all transactions would need to have the same tags, but I'm not sure how Power BI and Excel would deal with such differences in practice 🙃

gxander85

comment created time in 2 months

issue commentup-banking/api

Tagged Transactions

This seems very specific this particular integration.

The relationship between transactions and tags is a to many relationship, so defining tags as an array would be correct.

I'd need to understand more about why the array poses a problem for your particular scenario here, but it doesn't seem like an issue with the API as opposed to what assumptions this software is making about the shape of that data. If you need to flatten this relationship out, is it not possible to simply do something along the lines of tags.data.map(t => t.id) in the particular programming environment you have available to you?

gxander85

comment created time in 2 months

issue commentup-banking/api

Tagged Transactions

Can you clarify what you mean? I'm not clear on this:

Multiple Tags generate multiple lines for the same transactions.

We wouldn't be able to comma-separate, as comma is an allowable character in tags.

gxander85

comment created time in 2 months

issue closedup-banking/api

Query Unsettled/Pending Transactions

Is it Possible to just query the Unsettled or Pending transactions by Status?

        {
            "id": "1Removedf",
            "type": "transactions",
            "attributes": {
                "status": "SETTLED",
                "rawText": "GUZMAN Y GOMEZ, XXXXXXXXX",
                "description": "Guzman y Gomez",
                "message": null,

closed time in 2 months

yogeshpathade

issue commentup-banking/api

Query Unsettled/Pending Transactions

This one has now been added. ?filter[status]=HELD, for example.

yogeshpathade

comment created time in 2 months

push eventup-banking/api

d11wtq

commit sha c4237078a28cbb502cc58e5831f7e3a001f8abaf

Update OAS JSON to Latest Snapshot. Adds transaction status filter.

view details

push time in 2 months

issue commentup-banking/api

🚀 Up API Changelog

d11wtq

comment created time in 2 months

issue commentup-banking/api

Account Reconciliation Variance

Hi @gxander85 let me look into this for you 🤔

Would you mind sending a message via Talk to Us in the app, with a link to this Github issue, so I can get your account details confidentially and try and work out what's going on.

gxander85

comment created time in 2 months

pull request commentup-banking/api

Add Up Api web example

Thank you ❤️

svnm

comment created time in 2 months

push eventup-banking/api

Steven Martin

commit sha 25ac63a76fe41d7afe534183fa4f62cfe2a074b7

Add Up Api web example

view details

Chris Corbyn

commit sha 8a90f7ed979816b3ef899122b48956e271d39894

Merge pull request #42 from svnm/master Add Up Api web example

view details

push time in 2 months

PR merged up-banking/api

Add Up Api web example

Add Up Api web example using next.js

+10 -0

0 comment

1 changed file

svnm

pr closed time in 2 months

issue closedup-banking/api

How do I see Categories or Tags for transactions?

Hi,

I'm really keen to be able to see a spending breakdown over the year by Categories or Tags. Anyway to see the tags I've allocated to my transactions?

closed time in 2 months

scottgbailey

issue commentup-banking/api

How do I see Categories or Tags for transactions?

Both categories and tags are in production as of last week. Will close this one off.

scottgbailey

comment created time in 2 months

issue closedup-banking/api

Add Documentation Around URL Encoding of Example Parameters

In the docs, query parameters are intentionally formatted to be human readable. In some cases (particularly with RFC3339 timestamps, which include the + character) this means copy & paste won't result in a valid query parameter. We need to explicitly call out in the docs that query parameters must be correctly URL encoded.

Probably add an intro section about this, along with a disclaimer alongside each query parameter example. Ideally we'll adjust our curl examples to include valid representations of these parameters in the example request.

closed time in 2 months

d11wtq

issue commentup-banking/api

Add Documentation Around URL Encoding of Example Parameters

This should be in production in the next 30 mins or so.

d11wtq

comment created time in 2 months

push eventup-banking/api

Josh Willox

commit sha b9b98d1ca3d12a6a4dc88bea28c642bd732d5b8f

Add `up-bank-api` to examples

view details

Chris Corbyn

commit sha af11bb5cfff1f807a19e4b0f3b24b447cd5068a0

Merge pull request #40 from jcwillox/patch-1 Add `up-bank-api` to examples

view details

push time in 2 months

PR merged up-banking/api

Add `up-bank-api` to examples
+9 -0

0 comment

1 changed file

jcwillox

pr closed time in 2 months

issue commentup-banking/api

🚀 Up API Changelog

A few changes over the last week:

We're working on filtering by category and adding/removing categories to/from transactions.

d11wtq

comment created time in 2 months

issue closedup-banking/api

Incorrect description for `tags/delete`

Hi there! I'm loving this API documentation.

It looks like there is an error on the description field for the delete method on /transactions/{transactionId}/relationships/tags. The text of the description refers to webhooks, rather than tags. Possibly this was accidentally copied from another field.

The line in question is here: https://github.com/up-banking/api/blob/master/v1/openapi.json#L1508

closed time in 2 months

hen-zone

issue commentup-banking/api

Incorrect description for `tags/delete`

Just pushed up the updated OAS blob now. Sorry about that 😅

hen-zone

comment created time in 2 months

push eventup-banking/api

d11wtq

commit sha 92ac370d0f47bc1eeec4f5df5f33301ab690ff3d

Update OAS JSON to Latest Snapshot. Adds categories and fixes some copy/paste issues with tags docs.

view details

push time in 2 months

issue commentup-banking/api

How do I see Categories or Tags for transactions?

Responded on the other issue regarding incorrect description on tags. Same reason: pending an export from upstream. Will get an update into this repo shortly 😎

scottgbailey

comment created time in 2 months

issue commentup-banking/api

Incorrect description for `tags/delete`

Hi @hen-zone apologies; this has been fixed upstream but the OAS hasn't been exported back to this repository. I will sort this out this morning. We should probably automate this!

hen-zone

comment created time in 2 months

issue commentup-banking/api

Upcoming

@gxander85 This is not currently implemented but it will most likely be implemented in the future. Will leave this open as a feature request so we can let you know once it's available.

gxander85

comment created time in 2 months

push eventup-banking/api

Janith Dissanayake

commit sha 8ef8ec1047c2a3170f30acc44bc02576a150274d

Update EXAMPLES.md

view details

Chris Corbyn

commit sha c17e3193b5da2bdfb5a71df7f22c0b69964d27f1

Merge pull request #38 from JDsnyke/master Update EXAMPLES.md

view details

push time in 2 months

PR merged up-banking/api

Update EXAMPLES.md
+9 -0

0 comment

1 changed file

JDsnyke

pr closed time in 2 months

issue closedup-banking/api

Sending Payments

I would like to automatically refunda PayId transaction that was made to my account. I suppose this is not possible at the moment. Is this something that you have planned on adding in the future?

closed time in 2 months

sebnil

issue commentup-banking/api

Sending Payments

Closing as duplicate of https://github.com/up-banking/api/issues/16

sebnil

comment created time in 2 months

issue closedup-banking/api

Filter queries not working

Hi All,

I cant seem to get filter queries to work. I'm simply working with,

curl https://api.up.com.au/api/v1/transactions -G -H "Authorization: Bearer up:yeah:mypat" -d "filter[since]=2020-01-01T01:02:03+10:00"

And I keep getting,

{"errors":[{"status":"400","title":"Invalid Parameter","detail":"invalid date-time value (must be rfc-3339)","source":{"parameter":"filter[since]"}}]}

I've double checked the date time value and different variations (this is taken directly from the examples on the api site)! Is there something else I'm doing wrong? 😕

closed time in 2 months

JDsnyke

issue commentup-banking/api

Filter queries not working

Closing and replacing with https://github.com/up-banking/api/issues/37

JDsnyke

comment created time in 2 months

issue openedup-banking/api

Add Documentation Around URL Encoding of Example Parameters

In the docs, query parameters are intentionally formatted to be human readable. In some cases (particularly with RFC3339 timestamps, which include the + character) this means copy & paste won't result in a valid query parameter. We need to explicitly call out in the docs that query parameters must be correctly URL encoded.

Probably add an intro section about this, along with a disclaimer alongside each query parameter example. Ideally we'll adjust our curl examples to include valid representations of these parameters in the example request.

created time in 2 months

issue commentup-banking/api

Refund a PayId (or any) transaction

Gotcha 👍 Currently at this stage payments are completely absent from the API, both in terms of their metadata and in terms of the ability to send them. You'll see payments listed in the list of transactions, but only the basic transaction data. Both the ability to send payments and to get the rich metadata associated with payments will come; we're just not at that stage yet.

sebnil

comment created time in 2 months

issue commentup-banking/api

Filter queries not working

I think what we'll do with the docs is we'll provide a readable (non-encoded) example alongside the filter, we'll explicitly state that it's not URL encoded for readability, then we'll adjust the full curl example to include that type of filter but correctly encoded so it should be copy/paste-able. If we URL encoded everything in the docs I think it would likely be more confusing what you're supposed to pass and generally you want to manually URL encoding and whatever client library you use would take the raw value and URL encode it for you.

JDsnyke

comment created time in 2 months

issue commentup-banking/api

Filter queries not working

@JDsnyke It'll be the + symbol. That's not a URL safe character (actually neither are the : and the [] but curl is likely encoding those for you and they'd most likely be accepted either way). You need to URL encode that + as %2B otherwise the server sees that as a space character. This is something on our TODO list to explicitly call out the need for proper URL encoding even if the examples in the docs don't encode simply for readability. Correctly encoded that timestamp would be difficult to read.

JDsnyke

comment created time in 2 months

issue commentup-banking/api

How do I see Categories or Tags for transactions?

Quick update. Categories are now returned on the transaction resource. You can get a full list from /api/v1/categories. Filtering and updating are not yet implemented but should follow.

scottgbailey

comment created time in 3 months

issue commentup-banking/api

Refund a PayId (or any) transaction

Hi @sebnil,

What do you mean by refund? You can't initiate refunds via the app neither. Refunds are generated externally.

We do plan to have the ability to make payments and transfers in the API (with some added safeguards) but not sure this is what you're referring to?

sebnil

comment created time in 3 months

issue commentup-banking/api

Feature request: Expose opaque cursors for each paginated result

:+1: Worth noting that from that specification, the presence of a cursor on every record is largely historical:

As this spec was created with Relay Classic in mind, it’s worth noting that Relay Legacy did not define startCursor and endCursor, and relied on selecting the cursor of each edge; Relay Modern began selecting startCursor and endCursor instead to save bandwidth (since it doesn’t use any cursors in between).

Relay these days just refers to the pageInfo to get a startCursor and endCursor. I'm still not sure what the practical use case would be for splitting a page in two and paginating from an arbitrary point within it, vs just supplying a different page size to begin with.

Understand the flexibility. I just can't see a real-world use case it solves, weighed against the downsides of exposing the underlying pagination strategy in the API and going against the use of HATEOAS to drive the navigation within the API.

aaronvanston

comment created time in 3 months

more